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/plugins/pierrejanineh/techdebtmcp/plugin)<a href="https://agentmods.dev/plugins/pierrejanineh/techdebtmcp/plugin"><img src="https://agentmods.dev/badge/plugins/pierrejanineh/techdebtmcp/plugin/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/plugins/pierrejanineh/techdebtmcp/plugin"><img src="https://agentmods.dev/badge/plugins/pierrejanineh/techdebtmcp/plugin.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
tech-debt-mcp 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
{
"$schema": "https://json.schemastore.org/claude-code-plugin-manifest.json",
"name": "tech-debt-mcp",
"displayName": "Tech Debt MCP",
"version": "2.1.0",
"description": "Static technical-debt analysis across 14 languages, exposed as MCP tools and resources (SQALE ratings, debt summaries, custom rules, dependency vulnerabilities).",
"author": {
"name": "Pierre Janineh",
"url": "https://github.com/PierreJanineh"
},
"homepage": "https://github.com/PierreJanineh/TechDebtMCP#readme",
"repository": "https://github.com/PierreJanineh/TechDebtMCP",
"license": "MIT",
"keywords": [
"mcp",
"tech-debt",
"static-analysis",
"code-quality",
"sqale"
],
"mcpServers": {
"tech-debt-mcp": {
"command": "npx",
"args": ["-y", "tech-debt-mcp@latest"]
}
}
}
What it installs
The manifest is a name and a version. 1 skill, 3 commands travel with it, and installing the plugin installs all of them — 108 tokens a session between them. Each is measured on its own page, and each can be installed alone.
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 · 28 lines scan A 04e1b8ebbdaa
tech-debt-mcp is a plugin published in the GitHub repository PierreJanineh/TechDebtMCP (7 stars, last pushed 2mo ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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 plugins, from other repositories
devharness
Run and debug a live app from inside Claude Code: breakpoints and variable inspection in Chrome and Node.js, managed dev servers, and replayable call history so setup is never re-driven by hand.
incident-response
Production incident management, triage workflows, and automated incident resolution.
polygraph
A polygraph for your state machine. The agent does the hard part for you: it instruments your code, builds any test doubles needed to run it, and captures real execution traces — then has an LLM derive a transition-function spec from the source (default: a SAM v2 strict-profile module with named…
rashomon
Evaluate prompts and skills through parallel execution comparison in git worktrees. Prompt optimization with BP-001009 patterns, skill creation/update with quality grading, and blind A/B evaluation.
interview-me
Deep-dive spec interviewer that produces production-grade specs through rigorous 1-on-1 interviews, with --verify drift detection against the codebase.
devlens
Codebase intelligence for AI agents. The /devlens skill teaches your agent to query a precomputed code graph (nodes, typed edges, technical/business/security summaries) via the bundled DevLens MCP server instead of grepping and reading whole files — for TypeScript, JavaScript, Python, Go, Rust, and Java repos, with…