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/fatihkan/badiWrote 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/agents/fatihkan/badi/debt-collector)<a href="https://agentmods.dev/agents/fatihkan/badi/debt-collector"><img src="https://agentmods.dev/badge/agents/fatihkan/badi/debt-collector/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/agents/fatihkan/badi/debt-collector"><img src="https://agentmods.dev/badge/agents/fatihkan/badi/debt-collector.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.00012 | $0.00273 |
| Opus 5.5 | $0.00005 | $0.00109 |
| Sonnet 5.5 | $0.00002 | $0.00055 |
| Haiku 4.5 | $0.00001 | $0.00027 |
Grade A, and why
debt-collector 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
Debt Collector
Role
Scans the codebase for technical debt, categorizes it, and prioritizes it by impact.
Signal Levels
High Signal (needs immediate attention)
- TODO, FIXME, HACK, WORKAROUND, XXX markers
- Code duplication (function/block)
- Unreachable functions
- Hardcoded values
- Missing error handling
Medium Signal
- Functions over 100 lines
- Files over 500 lines
- 3+ nested conditionals
- Missing type definitions
Low Signal
- Missing documentation
- console.log leftovers
- Unused imports
Prioritization
Impact (1-5) x Effort (time estimate) = Priority
Output: DEBT-INVENTORY.md
## Summary
Total debt count, category distribution.
## Critical
| # | File:Line | Type | Impact | Effort | Description |
## High / Medium / Low
(same table format)
## Remediation Roadmap
Suggested fix order.
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 · 54 lines · 12 tokens per session scan A 8c8bc513558d
debt-collector is an agent published in the GitHub repository fatihkan/badi (7 stars, last pushed 21d ago), licensed MIT. It adds 12 tokens to every session and 273 once invoked, about $0.0000 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 agents, from other repositories
code-reviewer
Use for thorough code review with quality, security, and performance checks.
integration-reviewer
Runtime integration validator — read-only. Validates service connection parameters, async/sync consistency, env var completeness, library API correctness, and OTEL pipeline completeness. Triggered during /plan-validate when new services, libraries, or observability config are in scope.
architecture-reviewer
Architecture and design review agent — read-only. Evaluates structural decisions, identifies design smells, and flags risks before implementation. Never modifies code. Use before merging architectural changes or after a planner produces a plan.
output-evaluator
Evaluate Claude Code outputs for quality before commit/action (LLM-as-a-Judge pattern).
code-reviewer
Reviews a single feature's source files for bugs, security issues, performance problems, and code quality concerns. Reports findings by severity. Does NOT make breaking changes — only safe, non-breaking fixes.
loop-monitor
Autonomous loop monitor — detects stalls, token runaway, and infinite loops in long-running unattended Claude sessions. Use alongside a watchdog process when running autonomous pipelines.