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 agents/tacoda/keystone/code-debtgit clone --depth 1 https://github.com/tacoda/keystoneWhat 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.00032 | $0.00528 |
| Opus 5 | $0.00016 | $0.00264 |
| Sonnet 5 | $0.00006 | $0.00106 |
| Haiku 4.5 | $0.00003 | $0.00053 |
Grade A, and why
code-debt 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 2d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- keystone-code-debt — 94% identical, 7 lines differ
What it actually says
Sensor: code-debt
Surfaces and categorizes debt in the codebase — the known-suboptimal code the team has chosen to live with, plus the shape of any new debt being added in the current diff.
Paired sensor: charter-debt — covers debt in the charter itself (stale rules, placeholder bootstrap, empty idiom dirs, etc.). The two are tracked separately on purpose.
- Trigger — audit (codebase-wide) and review (diff-scoped).
- Inputs —
git grepfor debt markers (TODO,FIXME,HACK,XXX,DEPRECATED), complexity hotspots from risk-fingerprint, and any debt items already listed incorpus/state/code-debt.md. - Exit condition — every surfaced item is categorized (see Categories) and either matched to an existing ledger entry or proposed as a new one.
- Output — table of debt items: location, category, severity, owner (if known), whether new in this diff.
- State writes — proposes a diff to
corpus/state/code-debt.md. User accepts or edits.
Categories
| Category | What it means |
|---|---|
| deliberate | Known-suboptimal, chosen as a tradeoff. Has an owner and a trigger for revisit. |
| drift | Was once fine; the surrounding code moved and left this stale. |
| shortcut | A recent shortcut taken under time pressure. |
| discovery | Newly noticed; not yet categorized. |
A TODO without a category is automatically discovery until debt-review triages it.
Severity
- load-bearing — change is dangerous; the surrounding region depends on this exact shape.
- noisy — adds review burden but doesn't constrain change.
- stale — no longer relevant; can be removed without thought.
Anti-noise rule
Don't surface TODO in vendored or generated code (anything excluded from lint). Don't surface debt the ledger already records unless its severity changed.
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.
- 2d ago First seen · 43 lines · 32 tokens per session scan A 39e4a85256a1
code-debt is an agent published in the GitHub repository tacoda/keystone (44 stars, last pushed 2mo ago), licensed MIT. It adds 32 tokens to every session and 528 once invoked, about $0.0002 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-30.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.