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/agentsea/flashbackerWrote 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/agentsea/flashbacker/debt-hunter)<a href="https://agentmods.dev/commands/agentsea/flashbacker/debt-hunter"><img src="https://agentmods.dev/badge/commands/agentsea/flashbacker/debt-hunter/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/agentsea/flashbacker/debt-hunter"><img src="https://agentmods.dev/badge/commands/agentsea/flashbacker/debt-hunter.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.00000 | $0.00693 |
| Opus 5.5 | $0.00000 | $0.00277 |
| Sonnet 5.5 | $0.00000 | $0.00139 |
| Haiku 4.5 | $0.00000 | $0.00069 |
Grade A, and why
debt-hunter 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 — 64 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Technical Debt Hunter
Ruthlessly hunt down technical debt, code quality issues, and lazy implementations using the hybrid AI+Computer operations pattern.
Description
Scans the codebase for technical debt patterns using programmatic detection (ripgrep), then provides intelligent analysis and prioritized recommendations for cleanup.
Hybrid Pattern: CLI handles consistent pattern scanning, AI provides expert analysis and cleanup strategies.
Detection Patterns
Basic Technical Debt
- TODO/FIXME comments - Incomplete work markers
- Console debug logs - Debug artifacts left in code
- Not implemented functions - Empty or placeholder implementations
- Commented code blocks - Dead code that should be removed
- Generic variable names - Lazy naming (data, item, thing, stuff)
- Empty functions - Functions with no implementation
- Debugger statements - Breakpoints left in production code
- AI naming patterns - Similar function names (handle*, process*, manage*)
Duplicate Function Detection (Limited Heuristics)
- Exact duplicates - MD5 hash comparison of function signatures
- Similar names - AI-generated patterns like handleData/processData/manageData
- Near-duplicates - 80%+ text similarity in function bodies
- ⚠️ Limitations: Cannot detect semantic similarity or refactored duplicates
Usage
/fb:debt-hunter [scan_focus]
Examples:
/fb:debt-hunter- Full technical debt scan and analysis/fb:debt-hunter high-priority- Focus on high-severity issues only/fb:debt-hunter duplicates- Focus on duplicate function detection/fb:debt-hunter comprehensive- Run both basic patterns and duplicate detection
CLI Commands Available:
flashback debt-hunter --scan- Basic technical debt patternsflashback debt-hunter --duplicates- Duplicate/similar function detection (realistic heuristics only)flashback debt-hunter --context- Output structured context for AI analysis
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 · 64 lines · 0 tokens per session scan A ba0a488c4566
debt-hunter is a command published in the GitHub repository agentsea/flashbacker (57 stars, last pushed 9mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 693 tokens. 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 commands, from other repositories
refactor-clean
Refactor provided code for cleanliness, maintainability, and alignment with SOLID principles and modern best practices — no over-engineering.
deep-audit.skeleton
Description: This section is populated by Bootstrap with manifest data. Required manifest fields: project.description, stack.primary, project.structure, project.subprojects, stack.orm, stack.authmethod Example output.
harness:audit
Cross-dimensional codebase audit orchestrator — classify repo shape, fan out parallel read-only audit agents, dedup and severity-rank findings against existing issues, publish grouped tracking issues.
modify
Command "modify" from MartyBonacci/specswarm, covering user input, flag parsing, parse flags from arguments, mode routing and goal.
hotfix
Ship a fast branch-based P0 hotfix — diagnose, implement, open a ready-for-review PR, then verify + review after (deferred by design).
Diagnose
Run a 20-point health check across the plugin install, project config, PM/notification reachability, docs freshness, board consistency, and git state. Read-only — never changes state. Reports each check as PASS/WARN/FAIL/SKIP with an actionable fix. Target under 15 seconds end-to-end. Use before demos, after a plugin…