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-summarygit 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-summary)<a href="https://agentmods.dev/commands/pierrejanineh/techdebtmcp/techdebt-summary"><img src="https://agentmods.dev/badge/commands/pierrejanineh/techdebtmcp/techdebt-summary.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.00028 | $0.00535 |
| Opus 5 | $0.00014 | $0.00267 |
| Sonnet 5 | $0.00006 | $0.00107 |
| Haiku 4.5 | $0.00003 | $0.00053 |
Grade A, and why
techdebt-summary 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.
What it actually says
Fetch and display the aggregate technical-debt summary for a project.
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__get_debt_summarywith{ "path": "<resolved-path>" }. -
Before calling
mcp__tech-debt-mcp__get_sqale_metrics, ask the user: "Do you want the debt ratio as a percentage? If yes, provide your estimated total development time in hours." If they provide a number, include"developmentTime": <hours>in the next call; otherwise omit it. Then callmcp__tech-debt-mcp__get_sqale_metricswith{ "path": "<resolved-path>" }(anddevelopmentTimeif provided). This way the scan runs only once regardless of whether debt ratio is requested. -
Present a concise dashboard:
- Health score (0–100) and its grade, computed from the numeric score using this deterministic mapping: A (≥ 90), B (70–89), C (50–69), D (25–49), E (< 25). Do not guess — derive the grade directly from the number.
- SQALE rating (A–E) and debt ratio (shown as a percentage if
developmentTimewas supplied, otherwise N/A). - Issue counts by severity: critical / high / medium / low.
- Total estimated remediation time.
-
Suggest running
/techdebt-scanfor the full issue list or/techdebt-file <path>to drill into a specific file.
Notes
- This command intentionally omits individual file-level findings — use
/techdebt-scanfor those. - Do not duplicate MCP tool logic — all data is fetched by
mcp__tech-debt-mcp__get_debt_summaryandmcp__tech-debt-mcp__get_sqale_metrics. - If the path is not absolute, ask the user 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.
- 5d ago First seen · 32 lines · 28 tokens per session scan A 30877395ce81
techdebt-summary is a command published in the GitHub repository PierreJanineh/TechDebtMCP (7 stars, last pushed 1mo ago), licensed MIT. It adds 28 tokens to every session and 535 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
compact-prep
Ask the agent to prepare for conversation compaction by updating any relevant state and providing guidance for the compaction agent and to kick off the session there after.
composite-actions
Generate, review, secure, and test composite GitHub Actions following best practices — full repo scaffold, interview-driven generation, PR creation on existing repos, SHA pinning, secrets-as-inputs, job summaries, and actionlint validation.
aws
Structured guidance for AWS CloudFront distributions, WAF web ACLs, Lambda@Edge, CloudFront Functions, Firewall Manager multi-account enforcement, and IAM/IRSA patterns. Covers OAC, cache policies, security headers, managed rule groups, rate limiting, FMS FIRST/MIDDLE/LAST ownership model, and production-ready…
github-actions
Design, review, secure, and debug GitHub Actions workflows — reusable workflows, OIDC federation, SHA pinning, token scoping, promotion orchestration, and CI failure diagnosis.
datadog
Set up and troubleshoot Datadog — Agent deployment on Kubernetes, APM instrumentation, Log Management, Monitors, Dashboards, SLOs, Synthetic tests, and live incident investigation using the Datadog MCP server. Covers Terraform-managed Datadog resources.
fluxcd
FluxCD entry point — routes to the right workflow based on what you need. Live cluster issue → structured 5-workflow debug trace. Repo health check → 6-phase audit (discovery, validation, API compliance, best practices, security). Helm chart review → helmchart. Starts by asking one question to confirm the right mode.