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/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-file)<a href="https://agentmods.dev/commands/pierrejanineh/techdebtmcp/techdebt-file"><img src="https://agentmods.dev/badge/commands/pierrejanineh/techdebtmcp/techdebt-file/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/pierrejanineh/techdebtmcp/techdebt-file"><img src="https://agentmods.dev/badge/commands/pierrejanineh/techdebtmcp/techdebt-file.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.00022 | $0.00263 |
| Opus 5.5 | $0.00009 | $0.00105 |
| Sonnet 5.5 | $0.00004 | $0.00053 |
| Haiku 4.5 | $0.00002 | $0.00026 |
Grade A, and why
techdebt-file 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.
What it actually says
Analyze a single file for technical debt using the tech-debt-mcp analyzer.
Steps
-
Resolve the file path from
$ARGUMENTS.- The path must be absolute. If the user supplied a relative path, resolve it against the current working directory and confirm with the user before proceeding.
-
Call
mcp__tech-debt-mcp__analyze_filewith{ "path": "<absolute-file-path>" }. -
Present the results:
- File name, detected language, and total issue count.
- A table of issues sorted by severity (critical first), including: line number, severity, category, title, effort (if present), and suggested fix.
-
If no issues are found, say so — do not invent issues.
Notes
- Do not duplicate MCP tool logic — all analysis is performed by
mcp__tech-debt-mcp__analyze_file. - If no argument is provided, ask the user for the absolute path to the file they want to analyze.
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 · 26 lines · 22 tokens per session scan A e03c6d3438dd
techdebt-file is a command published in the GitHub repository PierreJanineh/TechDebtMCP (7 stars, last pushed 3mo ago), licensed MIT. It adds 22 tokens to every session and 263 once invoked, about $0.0001 per session on Opus 5.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
code-review
Review code for bugs, improvements, and best practices with actionable feedback.
review_code
Use the text the user typed after the command name as the request for this command.
review
Review a skill for quality before merge.
ingest-cwe-taxonomies
Ingest CWE XML from MITRE and generate per-domain security audit taxonomies for PromptKit.
boot
Start a new PromptKit prompt assembly session (alias for /bootstrap).
review
Review the current diff against project memory.