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/dokkabei97/forged-claude-code/tech-debt-trackergit clone --depth 1 https://github.com/Dokkabei97/forged-claude-codeWrote 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/dokkabei97/forged-claude-code/tech-debt-tracker)<a href="https://agentmods.dev/commands/dokkabei97/forged-claude-code/tech-debt-tracker"><img src="https://agentmods.dev/badge/commands/dokkabei97/forged-claude-code/tech-debt-tracker.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.00032 | $0.00683 |
| Opus 5 | $0.00016 | $0.00342 |
| Sonnet 5 | $0.00006 | $0.00137 |
| Haiku 4.5 | $0.00003 | $0.00068 |
Grade A, and why
tech-debt-tracker 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 — 98 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/tech-debt-tracker - Technical Debt Scanner
Triggers
- Periodic codebase health check
- Before sprint planning to assess debt paydown
- After rapid development phase to understand accumulated debt
Usage
/tech-debt-tracker
/tech-debt-tracker --path src/
/tech-debt-tracker --severity high
Behavioral Flow
Phase 1: Scan Codebase
Grep: "TODO|FIXME|HACK|WORKAROUND|XXX|TEMP" → Code markers
Grep: "eslint-disable|noqa|noinspection|@suppress" → Suppressed warnings
Grep: "any" in TypeScript files → Type safety gaps
Glob: package.json, requirements.txt → Check dependency age
Phase 2: Categorize Debt
| Category | Detection Method |
|---|---|
| Code Markers | TODO/FIXME/HACK comments |
| Suppressed Warnings | eslint-disable, noqa, etc. |
| Type Safety | any types, missing types |
| Outdated Deps | npm outdated / pip list --outdated |
| Dead Code | Unused exports, unreachable code |
| Duplication | Similar code blocks |
| Complexity | Functions > 50 lines, deep nesting |
Phase 3: Generate Report
# Tech Debt Report — YYYY-MM-DD
## Summary
| Category | Count | Severity |
|----------|-------|----------|
| Code Markers | [N] | 🟡 |
| Suppressed Warnings | [N] | 🟠 |
| Outdated Dependencies | [N] | 🟠 |
| Type Safety Gaps | [N] | 🟡 |
| **Total Items** | **[N]** | |
## High Priority (Fix This Sprint)
| # | File | Issue | Category |
|---|------|-------|----------|
| 1 | `path:line` | [Description] | [Category] |
## Medium Priority (Fix This Month)
...
## Low Priority (Backlog)
...
## Trend
[Compared to last scan: improving / stable / worsening]
## Recommended Actions
1. [Most impactful debt to pay down]
2. [Second priority]
Tool Coordination
- Grep: Search for debt markers and patterns
- Glob: Find files to scan
- Bash: Run
npm outdated,pip list --outdated - Write: Generate report
Boundaries
Will:
- Scan for common technical debt indicators
- Categorize and prioritize findings
- Track debt trends over time
- Suggest which debt to pay down first
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 · 98 lines · 32 tokens per session scan A ff6199d5a093
tech-debt-tracker is a command published in the GitHub repository Dokkabei97/forged-claude-code (2 stars, last pushed 6mo ago), licensed MIT. It adds 32 tokens to every session and 683 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-31.
Other commands, from other repositories
specify
Create or update the feature specification from a natural language feature description.
constitution
Create or update the project constitution from interactive or provided principle inputs.
plan
Execute the implementation planning workflow using the plan template to generate design artifacts.
speckit.bug.test
Validate that a previously fixed bug is resolved and record the verification report.
speckit.git.feature
Create a feature branch with sequential or timestamp numbering.
speckit.git.validate
Validate current branch follows feature branch naming conventions.