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 agents/kasuken/github-copilot-superpowers/tech-debt-remediation-plangit clone --depth 1 https://github.com/kasuken/github-copilot-superpowersWrote 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/agents/kasuken/github-copilot-superpowers/tech-debt-remediation-plan)<a href="https://agentmods.dev/agents/kasuken/github-copilot-superpowers/tech-debt-remediation-plan"><img src="https://agentmods.dev/badge/agents/kasuken/github-copilot-superpowers/tech-debt-remediation-plan.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.00477 |
| Opus 5 | $0.00010 | $0.00238 |
| Sonnet 5 | $0.00004 | $0.00095 |
| Haiku 4.5 | $0.00002 | $0.00048 |
Grade A, and why
Tech Debt Remediation Plan 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
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
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 · 44 lines · 19 tokens per session scan A d971c3532349
Tech Debt Remediation Plan is an agent published in the GitHub repository kasuken/github-copilot-superpowers (16 stars, last pushed 6mo ago), licensed MIT. It adds 19 tokens to every session and 477 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-30.
Other agents, from other repositories
VS Code Extension Developer
Use when: developing, debugging, testing, packaging, or reviewing VS Code extensions; package.json contributions, activation events, commands, views, webviews, language model tools, extension tests, esbuild, vsce, Marketplace readiness.
Fullstack Developer
End-to-end feature owner with expertise across the entire stack. Delivers complete solutions from database to UI with focus on seamless integration and optimal user experience.
Security Engineer
Expert infrastructure security engineer specializing in DevSecOps, cloud security, and compliance frameworks. Masters security automation, vulnerability management, and zero-trust architecture with emphasis on shift-left security practices.
Typescript Pro
Expert TypeScript developer specializing in advanced type system usage, full-stack development, and build optimization. Masters type-safe patterns for both frontend and backend with emphasis on developer experience and runtime safety.
API Designer
API architecture expert designing scalable, developer-friendly interfaces. Creates REST and GraphQL APIs with comprehensive documentation, focusing on consistency, performance, and developer experience.
Backend Developer
Senior backend engineer specializing in scalable API development and microservices architecture. Builds robust server-side solutions with focus on performance, security, and maintainability.