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 skills add patricio0312rev/skillset --skill tech-debt-prioritizergit clone --depth 1 https://github.com/patricio0312rev/skillsetWrote 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/skills/patricio0312rev/skillset/tech-debt-prioritizer)<a href="https://agentmods.dev/skills/patricio0312rev/skillset/tech-debt-prioritizer"><img src="https://agentmods.dev/badge/skills/patricio0312rev/skillset/tech-debt-prioritizer/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/skills/patricio0312rev/skillset/tech-debt-prioritizer"><img src="https://agentmods.dev/badge/skills/patricio0312rev/skillset/tech-debt-prioritizer.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.00055 | $0.01918 |
| Opus 5 | $0.00028 | $0.00959 |
| Sonnet 5 | $0.00011 | $0.00384 |
| Haiku 4.5 | $0.00006 | $0.00192 |
Grade A, and why
tech-debt-prioritizer 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 12d 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.
This is a copy
100% identical to tech-debt-prioritizer — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 330 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Tech Debt Prioritizer
Systematically prioritize and pay down technical debt.
Scoring Rubric
Impact Score (1-10)
10 - Critical:
- Prevents new features
- Causes frequent prod incidents
- Blocks multiple teams
7-9 - High:
- Significantly slows development
- Causes occasional incidents
- Affects one team heavily
4-6 - Medium:
- Moderate development friction
- Rare incidents
- Workarounds exist
1-3 - Low:
- Minor annoyance
- No incidents
- Easy workarounds
Risk Score (1-10)
10 - Critical:
- Security vulnerability
- Data integrity issues
- Legal/compliance risk
7-9 - High:
- Potential data loss
- System instability
- Vendor end-of-life soon
4-6 - Medium:
- Performance degradation
- Occasional failures
- Deprecated but working
1-3 - Low:
- Code quality issues
- Minor bugs
- Style inconsistencies
Effort Score (1-10)
10 - Herculean:
- 3+ months
- Multiple teams
- High risk changes
7-9 - Large:
- 1-3 months
- One team
- Medium risk
4-6 - Medium:
- 1-4 weeks
- 1-2 developers
- Low risk
1-3 - Small:
- Days
- Single developer
- Very low risk
Priority Formula
Priority Score = (Impact * 2 + Risk * 1.5) / Effort
Higher score = Higher priority
Tech Debt Inventory
| ID | Title | Impact | Risk | Effort | Score | Owner |
| ------ | ---------------------- | ------ | ---- | ------ | ----- | --------- |
| TD-001 | Legacy auth system | 9 | 10 | 8 | 3.7 | Auth Team |
| TD-002 | No database indexes | 8 | 7 | 3 | 7.8 | Backend |
| TD-003 | Monolithic build | 7 | 4 | 6 | 4.0 | DevOps |
| TD-004 | Duplicate API logic | 6 | 3 | 4 | 4.1 | Backend |
| TD-005 | Outdated dependencies | 5 | 8 | 2 | 9.0 | All Teams |
| TD-006 | Missing error handling | 4 | 6 | 3 | 5.7 | Backend |
| TD-007 | Poor test coverage | 4 | 5 | 7 | 2.3 | All Teams |
| TD-008 | Inconsistent naming | 3 | 2 | 5 | 1.6 | Frontend |
**Sorted by Priority Score:**
1. TD-005: Outdated dependencies (9.0)
2. TD-002: No database indexes (7.8)
3. TD-006: Missing error handling (5.7)
4. TD-004: Duplicate API logic (4.1)
5. TD-003: Monolithic build (4.0)
...
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.
- 12d ago First seen · 330 lines · 55 tokens per session scan A 1ccc98b37523
tech-debt-prioritizer is a skill published in the GitHub repository patricio0312rev/skillset (6 stars, last pushed 8mo ago), licensed MIT. It adds 55 tokens to every session and 1,918 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to tech-debt-prioritizer, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…