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.
npx agentmods add commands/stilero/claude-plugins/tech-debt-auditgit clone --depth 1 https://github.com/stilero/claude-pluginsWrote 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/stilero/claude-plugins/tech-debt-audit)<a href="https://agentmods.dev/commands/stilero/claude-plugins/tech-debt-audit"><img src="https://agentmods.dev/badge/commands/stilero/claude-plugins/tech-debt-audit.svg" alt="Measured on agentmods" 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 | $0.00052 | $0.02050 |
| Opus 5 | $0.00026 | $0.01025 |
| Sonnet 5 | $0.00010 | $0.00410 |
| Haiku 4.5 | $0.00005 | $0.00205 |
Grade A, and why
tech-debt-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 4d 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 — 237 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Tech Debt Audit
You are an audit orchestrator. You gather project context, spawn 11 specialized agents to audit the entire codebase in parallel, then merge their findings into a prioritized, deduplicated report grouped into actionable issues.
Step 1: Gather Project Context
Collect the following information to give all agents shared context:
# 1. Read project conventions
cat CLAUDE.md 2>/dev/null || echo "No CLAUDE.md found"
# 2. Read package manifest
cat package.json 2>/dev/null || cat web-server/package.json 2>/dev/null || echo "No package.json found"
# 3. Detect stack from dependencies and imports
grep -r "from ['\"]@prisma" src/ --include="*.ts" -l 2>/dev/null | head -5
grep -r "from ['\"]fastify" src/ --include="*.ts" -l 2>/dev/null | head -5
grep -r "from ['\"]express" src/ --include="*.ts" -l 2>/dev/null | head -5
# 4. File tree overview
find src -type f -name "*.ts" | grep -v node_modules | grep -v dist | head -200
# 5. Git churn analysis (most changed files = most likely to have debt)
git log --since="6 months ago" --format='' --name-only 2>/dev/null | sort | uniq -c | sort -rn | head -30
# 6. TypeScript config
cat tsconfig.json 2>/dev/null || echo "No tsconfig.json found"
Assemble this into a context preamble structured as:
## Project Context
- **Stack:** [detected frameworks and tools]
- **Conventions:** [key points from CLAUDE.md — legacy patterns to avoid, required patterns, architecture notes]
- **Source files:** [count of .ts files, main directories]
- **High-churn files:** [top 10 most-changed files in last 6 months]
- **TypeScript strictness:** [strict mode on/off, notable settings]
- **Dependencies:** [total count, notable frameworks with versions]
Step 2: Spawn 11 Audit Agents in Parallel
Launch ALL 11 agents in a SINGLE message using the Agent tool. Each agent receives:
- The context preamble from Step 1
- Their specialized audit instructions (from their agent definition)
- The shared output format
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.
- 4d ago First seen · 237 lines · 52 tokens per session scan A 7bdcf890a579
tech-debt-audit is a command published in the GitHub repository stilero/claude-plugins (2 stars, last pushed 2mo ago), licensed MIT. It adds 52 tokens to every session and 2,050 once invoked, about $0.0003 per session on Opus 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
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.