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/yeaight7/agent-powerupsWrote 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/yeaight7/agent-powerups/debt-audit)<a href="https://agentmods.dev/commands/yeaight7/agent-powerups/debt-audit"><img src="https://agentmods.dev/badge/commands/yeaight7/agent-powerups/debt-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/yeaight7/agent-powerups/debt-audit"><img src="https://agentmods.dev/badge/commands/yeaight7/agent-powerups/debt-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.00016 | $0.00197 |
| Opus 5.5 | $0.00006 | $0.00079 |
| Sonnet 5.5 | $0.00003 | $0.00039 |
| Haiku 4.5 | $0.00002 | $0.00020 |
Grade A, and why
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 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.
What it actually says
Technical Debt Audit
You are an architecture auditor. Your objective is to analyze the provided components or project context to quantify technical debt and propose a realistic plan for paying it down.
Target
$ARGUMENTS
Audit Guidelines
- Identify Constraints: Look for tightly coupled modules, deprecated library usage, and areas lacking test coverage.
- Categorize Debt: Group your findings into Code, Architecture, Infrastructure, and Testing debt.
- Assess Impact: Rate each finding based on its risk to production stability and its drag on development velocity.
- Remediation Plan: Output a prioritized roadmap. Break down large initiatives into atomic, safe steps that can be tackled in individual pull requests.
Provide actionable insights over generic advice. If applicable, suggest automated gates (e.g., linting rules, coverage thresholds) to prevent the debt from accumulating further.
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 · 21 lines · 16 tokens per session scan A baa7776d9542
debt-audit is a command published in the GitHub repository yeaight7/agent-powerups (7 stars, last pushed 25d ago), licensed Apache-2.0. It adds 16 tokens to every session and 197 once invoked, about $0.0001 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
t800-fix
A command for making a narrow, predefined fix to existing agents, skills, commands, rules, or hooks. A fix-pack is a file listing the exact changes to make.
t800-doctor
A command that runs a scripts-only health report for a T-800 or target plugin setup. It reports the version, profile, memory location, state, item counts, always-applied items, and recent audits.
t-800-factory-validate
A validation command for T-800 Factory files. It runs checks on agents and examines the graph of how those agents connect.
debug-trace
Analyze error and trace execution path to identify root cause.
cpp-build
Fix C++ build errors, CMake issues, and linker problems incrementally. Invokes the cpp-build-resolver agent for minimal, surgical fixes.
go-build
Fix Go build errors, go vet warnings, and linter issues incrementally. Invokes the go-build-resolver agent for minimal, surgical fixes.