Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/telus-labs/stagecraftWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/commands/telus-labs/stagecraft/audit)<a href="https://agentmods.dev/commands/telus-labs/stagecraft/audit"><img src="https://agentmods.dev/badge/commands/telus-labs/stagecraft/audit/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/telus-labs/stagecraft/audit"><img src="https://agentmods.dev/badge/commands/telus-labs/stagecraft/audit.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00078 | $0.01612 |
| Opus 5.5 | $0.00031 | $0.00645 |
| Sonnet 5.5 | $0.00016 | $0.00322 |
| Haiku 4.5 | $0.00008 | $0.00161 |
Grade A, and why
audit scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 165 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/audit
You are running a full codebase audit on this project.
Read .claude/skills/audit/SKILL.md before doing anything else. That file defines what each phase does, what each phase produces, and what inputs to gather before starting.
Input
The text after /audit is an optional scope constraint.
/audit— audit the entire codebase./audit src/backend/— focus the audit on one subtree./audit --resume— readdocs/audit/status.jsonand continue from the last completed phase.
Startup
Before any phase work:
- Read
.claude/skills/audit/SKILL.md(the phase definitions — the brain of this command). - Read
CLAUDE.mdif it exists (project-specific instructions). - Read
AGENTS.mdif it exists. - Create
docs/audit/if it doesn't exist. - Check for
docs/audit-extensions.md— note whether it exists; if it does, you'll read it at the start of each phase and append findings under a## Project-Specificheading in the phase's output file. - Run skill step 0.0 — archive any prior completed audit. If
docs/audit/status.jsonexists withcurrent_phase: "phase-3", move the prior audit's files intodocs/audit-archive/<date>-<version>-<context>/and append a row todocs/audit-archive/HISTORY.md. Skip on--resume. Full procedure inskills/audit/SKILL.md§ Phase 0 step 0.0. - Check for
docs/audit/status.json— if resuming, load state. Otherwise write a fresh status file:
{
"started": "<ISO 8601 timestamp>",
"scope": "full" | "scoped to <subtree>",
"phases": {
"phase-0": "pending",
"phase-1": "pending",
"phase-2": "pending",
"phase-3": "pending"
},
"current_phase": "phase-0",
"audited_by": "claude-code"
}
Execution
Run each phase as defined in .claude/skills/audit/SKILL.md. Read each phase's template (.claude/skills/audit/../templates/audit/<NN>-*.md — or copy the structure if your tools don't reach that path) before writing the output file.
Phase 0 — Bootstrap
Run steps 0.0 (archive prior audit), 0.1, 0.2, 0.3 from the skill. Write each output file.
If docs/audit-extensions.md declares Phase 0 extensions, run them and append results under ## Project-Specific in each phase-0 file.
Update status.json: "phase-0": "complete".
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 1mo ago First seen · 165 lines · 78 tokens per session scan A 85bcd4af9e2f
audit is a command published in the GitHub repository telus-labs/stagecraft (6 stars, last pushed 19d ago), licensed MIT. It adds 78 tokens to every session and 1,612 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other commands, from other repositories
debug
Systematic debugging with hypotheses and evidence gathering.
improve
/improve Scan and fix all improvement categories /improve arch Architectural improvements only /improve duplication Duplicate code / abstraction consolidation /improve quality Code quality (GuardLoop patterns GL-01 through GL-10) /improve security Security posture improvements /improve --dry-run Show what would be…
debugger
You are the Support & Debug persona in the ColdStart workflow. You are a relentless bug hunter who refuses to accept vague issues, half-documented bugs, or silent failures. You operate under these core assumptions: no error is random, no user report is exaggerated, and every failure is traceable to a flaw in logic…
detectar-ambiguedad
Detectar ambigüedades y contradicciones en specs de forma exhaustiva.
diagnostico
Verificar la salud del setup de Don Cheli en el proyecto actual.
code-locate
Locate code paths and line ranges for a described behavior: up to 10 candidates with HIGH/MEDIUM/LOW confidence and a search trail, plus a proposed SOURCEOFTRUTH.md update. Use when the first question is where one specific behavior lives and paths are unknown. Do not use when paths are explicit, the codebase is tiny…