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/pierrejanineh/techdebtmcp/techdebt-scangit clone --depth 1 https://github.com/PierreJanineh/TechDebtMCPWrote 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/pierrejanineh/techdebtmcp/techdebt-scan)<a href="https://agentmods.dev/commands/pierrejanineh/techdebtmcp/techdebt-scan"><img src="https://agentmods.dev/badge/commands/pierrejanineh/techdebtmcp/techdebt-scan.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.1 | $0.00019 | $0.00361 |
| Opus 5 | $0.00010 | $0.00180 |
| Sonnet 5 | $0.00004 | $0.00072 |
| Haiku 4.5 | $0.00002 | $0.00036 |
Grade A, and why
techdebt-scan 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 6d 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
Scan the project for technical debt using the tech-debt-mcp analyzer.
Steps
-
Resolve the project path:
- If the user supplied a path argument (
$ARGUMENTS), use it as-is (it must be an absolute path). - Otherwise, use the current working directory.
- If the user supplied a path argument (
-
Call
mcp__tech-debt-mcp__analyze_projectwith{ "path": "<resolved-path>" }. -
Call
mcp__tech-debt-mcp__get_sqale_metricswith{ "path": "<resolved-path>" }. -
Present a concise summary:
- Health score (from
mcp__tech-debt-mcp__analyze_project) and SQALE rating (frommcp__tech-debt-mcp__get_sqale_metrics). - Total issue count broken down by severity (critical / high / medium / low).
- Estimated total remediation time.
- Top 5 issues ranked by severity from the
mcp__tech-debt-mcp__analyze_projectresults, including file, line, and a one-line fix hint.
- Health score (from
-
Offer to dive deeper into any specific file, category, or severity if the user wants more detail.
Notes
- Do not duplicate MCP tool logic — all analysis is performed by the tools above.
- If the path is not an absolute path, tell the user and ask for the absolute path before proceeding.
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.
- 6d ago First seen · 31 lines · 19 tokens per session scan A 5afe230d0cc9
techdebt-scan is a command published in the GitHub repository PierreJanineh/TechDebtMCP (7 stars, last pushed 1mo ago), licensed MIT. It adds 19 tokens to every session and 361 once invoked, about $0.0001 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
debug
Structured platform troubleshooting — classifies the problem layer, collects evidence, forms a root-cause hypothesis, and proposes a fix with validation and rollback steps.
linkerd
Linkerd-specific diagnostics — mTLS verification, proxy injection issues, authorization policy debugging, traffic management, and multi-cluster connectivity problems.
findcode
Find one function or class and show its code.
lint
Run linting across the project.
check-cache
Audit caching configuration in $ARGUMENTS for Next.js 15 correctness.
fix_issue
Use the text the user typed after the command name as the request for this command.