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/liortesta/clawdagent/techdebtgit clone --depth 1 https://github.com/liortesta/ClawdAgentWhat 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.00000 | $0.00448 |
| Opus 5 | $0.00000 | $0.00224 |
| Sonnet 5 | $0.00000 | $0.00090 |
| Haiku 4.5 | $0.00000 | $0.00045 |
Grade A, and why
techdebt 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.
What it actually says
Tech Debt Hunter
Find high-leverage technical debt improvements in the codebase.
Scan Process:
- Code Duplication: Find duplicated code blocks (>10 lines repeated)
- Long Functions: Find functions >50 lines that should be split
- Missing Error Handling: Find try/catch gaps, unhandled promises, missing null checks
- TODO/FIXME/HACK: Find all tech debt markers with their context
- Dead Code: Find unused exports, unreachable code, unused dependencies
- Type Safety: Find
anytypes, type assertions, missing types - Test Gaps: Find untested critical paths
Scoring:
For each finding, evaluate:
- Impact: How much does fixing this improve the codebase? (1-10)
- Risk: How risky is the current state? (1-10)
- Effort: How much work to fix? (S/M/L/XL)
- ROI: Impact / Effort — higher is better
Output Format:
## Tech Debt Report
### Top 5 High-ROI Improvements
#### 1. [Title] (ROI: X/10)
- **Location**: [file:line]
- **Problem**: [what's wrong]
- **Impact**: X/10 — [why it matters]
- **Risk**: X/10 — [what could go wrong]
- **Effort**: [S/M/L/XL]
- **Fix**: [specific steps to resolve]
- **Verification**: [how to verify the fix]
...
### Summary
- Total tech debt items found: X
- Critical (fix now): X
- Important (fix this sprint): X
- Nice to have (backlog): X
- Estimated total effort: X hours
Rules:
- Focus on TOP 5 highest ROI items — don't overwhelm with every minor issue
- ALWAYS provide specific file:line references
- ALWAYS include verification steps
- Rank by effort-to-impact ratio, not just severity
$ARGUMENTS
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 · 53 lines · 0 tokens per session scan A 469818eab19c
techdebt is a command published in the GitHub repository liortesta/ClawdAgent (11 stars, last pushed 5d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 448 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
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
constitution
Create or update the project constitution from interactive or provided principle inputs.