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 Vimalk0703/shipworthy --skill tech-debt-trackinggit clone --depth 1 https://github.com/Vimalk0703/shipworthyWrote 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/vimalk0703/shipworthy/tech-debt-tracking)<a href="https://agentmods.dev/skills/vimalk0703/shipworthy/tech-debt-tracking"><img src="https://agentmods.dev/badge/skills/vimalk0703/shipworthy/tech-debt-tracking/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/vimalk0703/shipworthy/tech-debt-tracking"><img src="https://agentmods.dev/badge/skills/vimalk0703/shipworthy/tech-debt-tracking.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.00024 | $0.00491 |
| Opus 5.5 | $0.00010 | $0.00196 |
| Sonnet 5.5 | $0.00005 | $0.00098 |
| Haiku 4.5 | $0.00002 | $0.00049 |
Grade A, and why
tech-debt-tracking 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
Tech Debt Tracking
Purpose
Every shortcut has a cost. This skill ensures shortcuts are conscious decisions with documented justifications, not accidents that compound silently.
When to Track
- Skipping tests for time pressure
- Using a workaround instead of a proper fix
- Hardcoding a value that should be configurable
- Writing a TODO comment
- Bypassing a quality gate with justification
- Using a deprecated API or pattern
- Choosing a quick solution over the correct one
How to Track
Add an entry to .shipworthy/tech-debt.md:
## [Short Description]
- **Date**: YYYY-MM-DD
- **Severity**: low | medium | high | critical
- **Effort to fix**: hours | days | weeks
- **Justification**: Why was this shortcut taken?
- **Impact if not fixed**: What happens if this stays forever?
- **Files affected**: List specific files
Rules
- Every shortcut requires justification — "I didn't have time" is a valid justification, but document it
- No silent TODOs — every
TODOin code must have a corresponding entry in tech-debt.md - Review at session start — the session-start hook surfaces the debt count
- Debt has a severity — critical debt should be fixed before adding new features
- Debt has a shelf life — if it's been there >30 days with no plan to fix, escalate the conversation
When to Pay Down Debt
- Before starting a new feature in the same area
- When the debt is causing real problems (bugs, slowness, confusion)
- During dedicated refactoring time
- When the effort to work around the debt exceeds the effort to fix it
Anti-Patterns
- Tracking debt but never paying it down
- Not tracking debt at all ("we'll remember")
- Treating all debt as equal (prioritize by severity and impact)
- Using debt tracking as an excuse to write sloppy code ("I'll track it as debt")
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 · 58 lines · 24 tokens per session scan A 1cf19edaa930
tech-debt-tracking is a skill published in the GitHub repository Vimalk0703/shipworthy (6 stars, last pushed 6mo ago), licensed MIT. It adds 24 tokens to every session and 491 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-08-31.
Other skills, from other repositories
dare-refine
Analisa complexidade de uma task DARE e, quando alta, quebra em sub-tasks menores. Use após gerar o DAG (para tasks HIGH/CRITICAL), quando o dev pedir refinamento manual, ou quando o escopo mudou e uma task ficou grande. Combina heurística determinística (CLI) com decisão semântica do agente.
dare-dag
Mostra o DAG estático de tasks (DARE/dare-dag.yaml): ranks, dependências e caminho crítico. Use dare dag viz para exportar o diagrama. Mapeia o CLI dare dag.
dare-graph
Consulta e visualiza o grafo de conhecimento do projeto (tasks, arquivos, schemas, endpoints, componentes, entidades e suas relações). Mapeia o CLI dare graph.
team-qa
Orchestrate the QA team through a full testing cycle — qa-lead strategy and test plan, qa-tester case writing, execution, sign-off.
release-checklist
Pre-release checklist — build verification, certification requirements, store metadata, launch readiness.
bug-triage
Re-evaluate open bugs — priority vs severity, assign to sprints, surface systemic trends. Run when the count grows.