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/cassler/awesome-claude-code-setup/tech-debt-huntgit clone --depth 1 https://github.com/cassler/awesome-claude-code-setupWrote 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/cassler/awesome-claude-code-setup/tech-debt-hunt)<a href="https://agentmods.dev/commands/cassler/awesome-claude-code-setup/tech-debt-hunt"><img src="https://agentmods.dev/badge/commands/cassler/awesome-claude-code-setup/tech-debt-hunt.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.00000 | $0.00904 |
| Opus 5 | $0.00000 | $0.00452 |
| Sonnet 5 | $0.00000 | $0.00181 |
| Haiku 4.5 | $0.00000 | $0.00090 |
Grade A, and why
tech-debt-hunt 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 5d 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 — 125 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Technical Debt Assessment
Please help me identify and prioritize technical debt in ${FOCUS_AREA:-the entire codebase}.
Thresholds:
- File size: ${MAX_FILE_SIZE:-500} lines
- Complexity: ${MAX_COMPLEXITY:-15}
- TODO age: ${TODO_AGE_DAYS:-30} days
Debt Discovery
-
Find TODOs and FIXMEs:
# Get all TODOs with context ch cq todos --with-context # Find old TODOs (using git blame) chs find-code "TODO|FIXME|HACK|XXX" 2>/dev/null | while IFS= read -r file; do if [ -f "$file" ]; then echo "=== $file ===" git blame "$file" 2>/dev/null | grep -E "TODO|FIXME|HACK|XXX" || true fi done -
Identify large files:
# Find files exceeding threshold ch cq large-files ${MAX_FILE_SIZE:-500} # Show largest files first find . -name "*.${FILE_EXT:-js|ts|py}" -exec wc -l {} + | sort -rn | head -20 -
Find complex code:
# High cyclomatic complexity ch cq complexity ${MAX_COMPLEXITY:-15} # Deeply nested code chs find-code "^\\s{16,}" --files-with-matches # Long functions (multiple patterns) chs find-code "function.*\\{[^}]{500,}" -
Check for outdated patterns:
# Find deprecated usage chs find-code "@deprecated|DEPRECATED" # Old library usage chs find-code "${OLD_PATTERNS:-callback\\(err\\)|var\\s+\\w+\\s*=\\s*require}" -
Dependency debt:
# Check for outdated packages ch ts deps --outdated # Find security vulnerabilities ch ts audit # Look for multiple versions ch ts deps --duplicates -
Code duplication:
# Find similar patterns for pattern in "${DUPLICATE_PATTERNS[@]:-"function.*{" "class.*{" "interface.*{"}"; do echo "=== Checking pattern: $pattern ===" chs find-code "$pattern" --count | sort -rn | head -10 done -
Missing tests:
# Find untested files comm -23 \ <(find . -name "*.${FILE_EXT:-js}" | grep -v test | sort) \ <(chs find-file "*.test.*" | xargs grep -l "import\|require" | sort -u)
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.
- 5d ago First seen · 125 lines · 0 tokens per session scan A 84105da61dc9
tech-debt-hunt is a command published in the GitHub repository cassler/awesome-claude-code-setup (267 stars, last pushed 4mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 904 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
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.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.