Borrowing it
Nothing to install: this file belongs to davidruzicka/mcp4openapi. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/davidruzicka/mcp4openapi/main/.github/prompts/technical-debt.prompt.mdgit clone --depth 1 https://github.com/davidruzicka/mcp4openapiWrote 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/davidruzicka/mcp4openapi/technical-debt)<a href="https://agentmods.dev/commands/davidruzicka/mcp4openapi/technical-debt"><img src="https://agentmods.dev/badge/commands/davidruzicka/mcp4openapi/technical-debt/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/davidruzicka/mcp4openapi/technical-debt"><img src="https://agentmods.dev/badge/commands/davidruzicka/mcp4openapi/technical-debt.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.00013 | $0.00354 |
| Opus 5.5 | $0.00005 | $0.00142 |
| Sonnet 5.5 | $0.00003 | $0.00071 |
| Haiku 4.5 | $0.00001 | $0.00035 |
Grade A, and why
technical-debt 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
Technical Debt Remediation Plan
Generate comprehensive technical debt remediation plans. Analysis only - no code modifications. Keep recommendations concise and actionable. Do not provide verbose explanations or unnecessary details.
Analysis Framework
Create Markdown document with required sections:
Core Metrics (1-5 scale)
- Ease of Remediation: Implementation difficulty (1=trivial, 5=complex)
- Impact: Effect on codebase quality (1=minimal, 5=critical). Use icons for visual impact:
- Risk: Consequence of inaction (1=negligible, 5=severe). Use icons for visual impact:
- 🟢 Low Risk
- 🟡 Medium Risk
- 🔴 High Risk
Required Sections
- Overview: Technical debt description
- Explanation: Problem details and resolution approach
- Requirements: Remediation prerequisites
- Implementation Steps: Ordered action items
- Testing: Verification methods
Common Technical Debt Types
- Missing/incomplete test coverage
- Outdated/missing documentation
- Unmaintainable code structure
- Poor modularity/coupling
- Deprecated dependencies/APIs
- Ineffective design patterns
- TODO/FIXME markers
Output Format
- Summary Table: Overview, Ease, Impact, Risk, Explanation
- Detailed Plan: All required sections
GitHub Integration
- Use
search_issuesbefore creating new issues - Apply
/.github/ISSUE_TEMPLATE/chore_request.ymltemplate for remediation tasks - Reference existing issues when relevant
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 · 49 lines · 13 tokens per session scan A ea36d7fa9254
technical-debt is a command published in the GitHub repository davidruzicka/mcp4openapi (0 stars, last pushed 4d ago), licensed MIT. It adds 13 tokens to every session and 354 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-09-29.
Other commands, from other repositories
refactor
Systematic code refactoring with smart scope detection.
review-branch
Review the current branch's diff against base by dispatching atomic-reviewer. No orchestration loop, no spec required — pre-flight before /commit pr or /commit merge.
init
Install the formatters this repository needs, with every command visible before it runs.
spec-trace-requirements
You are verifying that implementation changes trace back to specification requirements.
merge-conflict-analysis
You are analyzing merge conflicts for PR #${{ pr-number }}.
boot
Start a new PromptKit prompt assembly session (alias for /bootstrap).