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 camilooscargbaptista/cto-toolkit --skill tech-debt-prioritizationgit clone --depth 1 https://github.com/camilooscargbaptista/cto-toolkitWrote 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/camilooscargbaptista/cto-toolkit/tech-debt-prioritization)<a href="https://agentmods.dev/skills/camilooscargbaptista/cto-toolkit/tech-debt-prioritization"><img src="https://agentmods.dev/badge/skills/camilooscargbaptista/cto-toolkit/tech-debt-prioritization/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/camilooscargbaptista/cto-toolkit/tech-debt-prioritization"><img src="https://agentmods.dev/badge/skills/camilooscargbaptista/cto-toolkit/tech-debt-prioritization.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.00023 | $0.01351 |
| Opus 5 | $0.00012 | $0.00675 |
| Sonnet 5 | $0.00005 | $0.00270 |
| Haiku 4.5 | $0.00002 | $0.00135 |
Grade A, and why
tech-debt-prioritization 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 9d 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.
How it starts
The opening of the file, as written. The whole thing — 158 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Tech Debt Prioritization
When to Use
- Sprint planning: deciding which tech debt to tackle
- Quarterly planning: allocating tech debt budget
- Stakeholder communication: justifying tech debt investment
- Codebase health assessment
Tech Debt Quadrant (Martin Fowler)
Deliberate Inadvertent
┌─────────────────────┬─────────────────────┐
Reckless │ "We don't have time │ "What's a │
│ for tests" │ repository pattern?"│
│ → High priority │ → Training need │
├─────────────────────┼─────────────────────┤
Prudent │ "Ship now, refactor │ "Now we know how │
│ next sprint" │ it should be done" │
│ → Track + schedule │ → Natural evolution │
└─────────────────────┴─────────────────────┘
Identification Checklist
Code-Level Debt
- Functions > 50 lines (complexity)
- Files > 500 lines (god class)
- Duplicated code (> 3 occurrences)
-
// TODO,// FIXME,// HACKcomments -
@ts-ignore,anytypes without justification - Tests with
.skip()or no assertions - Dead code (unused functions, unreachable branches)
Architecture-Level Debt
- Circular dependencies between modules
- Business logic in controllers/resolvers
- Database queries in non-repository layers
- Direct dependency on external services (no abstraction)
- Shared mutable state (global variables)
- Missing error boundaries
Infrastructure Debt
- Manual deployment steps
- Missing monitoring for critical paths
- No automated backups or disaster recovery
- Outdated dependencies (> 2 major versions behind)
- Missing rate limiting on public APIs
- No CI/CD pipeline
RICE Scoring for Prioritization
RICE Score = (Reach × Impact × Confidence) / Effort
Reach: How many users/developers are affected? (1-10)
Impact: How much does it improve things? (0.25=minimal, 0.5=low, 1=medium, 2=high, 3=massive)
Confidence: How sure are we of the estimates? (0.5=low, 0.8=medium, 1.0=high)
Effort: Person-weeks to complete (1=1 week, 2=2 weeks, etc.)
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.
- 9d ago First seen · 158 lines · 23 tokens per session scan A a8f987cd4f11
tech-debt-prioritization is a skill published in the GitHub repository camilooscargbaptista/cto-toolkit (7 stars, last pushed 5mo ago), licensed MIT. It adds 23 tokens to every session and 1,351 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 skills, from other repositories
refactoring-workflow
Improve the structure of existing code without changing its behaviour, in small verified steps under a green test suite. Use when the user asks to refactor, clean up, restructure or simplify code, wants to reduce duplication or coupling, is preparing a codebase for a feature it cannot currently accommodate, or when…
code-quality-review
A code-review guide for judging whether software stays easy to understand, change, test, and extend.
refactor
Refactors specified code to improve clarity, reduce duplication, or align with the project's architectural patterns — without changing external behavior. Invoked when the user asks to refactor, clean up, simplify, or restructure code.
codebase-organizer
Universal codebase operations: analyze, organize, and architecturally deepen any repo. Two commands: /organize for read-only analysis and /deepen for multi-agent refactoring. Use when the user wants a codebase scan, deep module scoring, dependency mapping, architectural improvement, or code-to-skill conversion.…
Tech Debt Auditor
Identifies and prioritizes technical debt in a codebase with an effort/impact matrix.
arch-optimize
A software architecture review workflow that scans a codebase for structural risks and measures code quality. It checks issues such as overly complex code, repeated knowledge, changes spreading across many files, circular dependencies, and distorted domain models.