TypingMindTypingMindThe best frontend for AI
Code Audit Brief Stinger logo

Code Audit Brief Stinger

Organization
legioncodeinc
code-audit-brief-stinger

Render the Audit My Code brief, one self-contained Field Guide styled HTML file per run, from the workspace only. Escapes repo text, merges duplicates, prints cleanly to PDF.

Overview

Publisherlegioncodeinc
Repositoryvibe-coding-tools
Skill namecode-audit-brief-stinger
Stars
94
Forks
44
Bundled files
17
LicenseAGPL-3.0-or-later
Links
Skill sourceRepository
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • 17 bundled files

    Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

  • Open source

    Published by legioncodeinc on GitHub. Read the source before you install it.

Installation

Install the Code Audit Brief Stinger AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/legioncodeinc/vibe-coding-tools/tree/main/plugins/code-audit-tools/skills/code-audit-brief-stinger
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/legioncodeinc/vibe-coding-tools.git /tmp/vibe-coding-tools
mkdir -p .claude/skills
cp -r /tmp/vibe-coding-tools/plugins/code-audit-tools/skills/code-audit-brief-stinger .claude/skills/code-audit-brief-stinger
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Code Audit Brief Stinger in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Code Audit Brief Stinger on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Code Audit Brief Stinger is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Code Audit Brief Stinger

Designed and built by Legion Code Inc.

Where this skill's files are

Every path below (guides/, references/, scripts/) is relative to the folder that contains this SKILL.md. In Claude Code that folder is ${CLAUDE_SKILL_DIR}. If that text was not replaced with a real path, find the folder with Glob for **/code-audit-brief-stinger/SKILL.md and use it in every command.

Purpose

Turn a finished /audit-my-code run workspace into one HTML brief at <workspace>/brief/brief.html that a founder can read on a phone or save as a PDF. The brief covers exactly the dimensions of the tier that ran, in the Legion Code Inc. Field Guide style: cover, the whole audit in one paragraph, a verdict scorecard, one part per dimension (measures, charts, findings, spot checks, tool limits), fix these first, coverage and caps, and the method and evidence index. It renders; it never invents, edits, or re-scores a finding.

When to use

  • "Render the brief", "build the audit report", "make the HTML for this audit run"
  • The last step of /audit-my-code after every dimension Drone has written its output
  • Re-rendering after a Drone fixes its findings.jsonl or metrics.json
  • Changing the brief's branding (palette, fonts, logos, footer) in one place

When not to use

  • Running any audit dimension: the foundation, bloat, security, quality, and remediation Drones own that
  • Website audit reports from crawled sites: audit-reporting-stinger
  • Scoring or weighting findings into a number: this brief uses the contract verdict scale only
  • Writing anything into the audited repository: this skill writes only brief/brief.html in the workspace

Procedure

  1. Read guides/00-inputs-and-contract.md and the contract it links. Confirm the workspace path and that intake.json exists.
  2. Run the contract checker if installed and note its failures for the orchestrator (guide 00).
  3. Render: python3 scripts/render_brief.py <workspace> (guide 02). Keep the summary line it prints.
  4. Check the brief against guides/04-verification-before-handoff.md and references/verification-checklist.md: tier coverage, not-run reasons, caps, escaping, phone width, print.
  5. Report the brief path, overall verdict, counts by severity, and every data check, naming the Drone that owns each problem. Never patch workspace files yourself.
  6. Branding change requested: follow guides/03-branding-system.md, edit only references/brand/brand.json and the logo files, re-render a fixture, and run python3 scripts/test_render_brief.py.

References map

PathLoad when
guides/00-inputs-and-contract.mdFirst, on every task
guides/01-section-map-per-tier.mdChecking which sections a tier gets or where a section's content comes from
guides/02-rendering-and-escaping.mdRunning or editing the renderer; any question about untrusted text
guides/03-branding-system.mdChanging palette, fonts, logos, footer, theme, or print look
guides/04-verification-before-handoff.mdBefore handing the brief to anyone
references/REFERENCE.mdScript options, files read, function contracts, fixtures
references/verification-checklist.mdThe tick list for guide 04
references/brand/brand.jsonThe single place to change branding
references/brand/*.svgLogo, symbol, and favicon inlined into the brief
references/fixtures/sample-*/Fictional workspaces and their rendered briefs, for testing changes
scripts/render_brief.pyRun to render; rollup_verdict sits near the top
scripts/test_render_brief.pyRun after any change to the script or the brand file
references/research/distilled-brief-rendering.mdVerifying a claim about print, tables, escaping, fonts, or the design sources
Source research archive (not shipped with the plugin)Source-repository only; the shipped distillation summarizes it, do not require it

Related drones and stingers

Critical Directive

  • You must read all files and context contained within your skill.
  • In the event your core knowledge does not provide sufficient guidance you must make every attempt to search the internet, related knowledge base documentation files, and other available resources to supplement your knowledge prior to proceeding with your task.
  • Additional related skills can be found here:

Designed and built by Legion Code Inc. Licensed under AGPL-3.0-or-later.

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Code Audit Brief Stinger AI skill do?

Render the Audit My Code brief, one self-contained Field Guide styled HTML file per run, from the workspace only. Escapes repo text, merges duplicates, prints cleanly to PDF.

Why use Code Audit Brief Stinger on TypingMind?

Because you install it once and use it with any model. Code Audit Brief Stinger is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Code Audit Brief Stinger in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/legioncodeinc/vibe-coding-tools/tree/main/plugins/code-audit-tools/skills/code-audit-brief-stinger. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Code Audit Brief Stinger?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Code Audit Brief Stinger?

As many as you like. As long as a model supports skills, you can use Code Audit Brief Stinger with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Code Audit Brief Stinger AI skill free?

Yes. It is published on GitHub by legioncodeinc under the AGPL-3.0-or-later license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

Related AI Skills

View all
vercel logo

Dce Edge

vercel
OrganizationPopular

DCE-safe require() patterns and edge runtime constraints. Use when writing conditional require() calls, guarding Node-only imports (node:stream etc.), or editing define-env-plugin.ts / app-render /…

34.7K
143.1K
Instructions
View
vercel logo

Gh Stack

vercel
OrganizationPopular

Manages stacked PRs and splits multi-part work into reviewable branches with gh-stack. Use for stack creation, viewing, edits, push, submit, sync, rebase, merge, or checkout; when asked to split or…

34.7K
143.1K
3 files
View
openclaw logo

Agent Transcript

openclaw
OrganizationPopular

Requested GitHub PR/issue agent transcripts: redact, trim, preview, and insert safely.

82.2K
391K
1 files
View
openclaw logo

Openclaw Refactor Docs

openclaw
OrganizationPopular

Refactor an existing OpenClaw docs page with source-audited preservation, restructuring, and verification.

82.2K
391K
Instructions
View

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇