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 Morningstar202604/awesome-skillkit --skill tech-debt-trackergit clone --depth 1 https://github.com/Morningstar202604/awesome-skillkitWrote 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/morningstar202604/awesome-skillkit/tech-debt-tracker)<a href="https://agentmods.dev/skills/morningstar202604/awesome-skillkit/tech-debt-tracker"><img src="https://agentmods.dev/badge/skills/morningstar202604/awesome-skillkit/tech-debt-tracker/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/morningstar202604/awesome-skillkit/tech-debt-tracker"><img src="https://agentmods.dev/badge/skills/morningstar202604/awesome-skillkit/tech-debt-tracker.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.00090 | $0.01744 |
| Opus 5.5 | $0.00036 | $0.00698 |
| Sonnet 5.5 | $0.00018 | $0.00349 |
| Haiku 4.5 | $0.00009 | $0.00174 |
Grade A, and why
tech-debt-tracker 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.
This is a copy
89% identical to tech-debt-tracker — 126 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 — 122 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Tech Debt Tracker
Scans a codebase for technical-debt signals, ranks the backlog using a cost-of-delay framework, and tracks trends from dated snapshots. This skill only tracks and plans debt-repayment work — it does not perform refactors.
Pipeline: debt_scanner.py → debt_prioritizer.py → debt_dashboard.py. The scanner's JSON output feeds the prioritizer directly; dated inventory snapshots feed the dashboard.
Input Checklist
| Input | Required | Description |
|---|---|---|
| Codebase directory | Required | The path passed to the scanner; must exist and be readable |
| Prioritization framework | Optional | cost_of_delay (default), wsjf, or rice |
--team-size |
Optional | Number of people for sprint allocation (prioritizer default: 5) |
--sprint-capacity |
Optional | Sprint capacity in hours (prioritizer default: 80) |
| Snapshot history | Optional | Dated inventory JSON (debt_YYYY-MM-DD.json) for trend tracking |
When inputs are missing, ask all at once: "Please provide: (1) the codebase directory to scan; (2) framework choice (cost_of_delay/wsjf/rice, default cost_of_delay); (3) team size and capacity for sprint allocation; (4) any historical snapshot files for trend analysis. Everything else uses defaults."
Pre-flight Checks
Probe each item; if any fails → give the fix and STOP:
python3 --version # expected 3.8+; failure: install python3
# Self-check: python3 scripts/debt_scanner.py --help / debt_prioritizer.py / debt_dashboard.py all expected to exit 0
test -d <codebase-directory> # expected exit code 0; failure: wrong path → ask the user for the correct directory
Workflow
Step 1: Scan the codebase
python3 scripts/debt_scanner.py examples/sample-codebase --format json --output snapshots/2026-09.json # bundled sample codebase; swap in your real codebase root
Expected: produce debt_inventory.json containing scan_metadata, summary, debt_items[], file_statistics, and recommendations. Report the summary counts to the user. To practice, point the scanner at assets/sample_codebase. On failure: debt_items[] is empty → the directory may have no scannable source files; confirm the path contains code, not just docs/config.
What ships with it
17 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- assets/historical_debt_2024-01-15.json 8.0 KB
- assets/historical_debt_2024-02-01.json 6.4 KB
- assets/sample_codebase/src/frontend.js 15 KB runs code
- assets/sample_codebase/src/payment_processor.py 13 KB runs code
- assets/sample_codebase/src/user_service.py 9.3 KB runs code
- assets/sample_debt_inventory.json 7.6 KB
- expected_outputs/sample_dashboard_output.json 5.2 KB
- expected_outputs/sample_prioritization_output.json 45 KB
- expected_outputs/sample_scan_output.json 57 KB
- README.md 9.3 KB
- references/debt-classification-taxonomy.md 10 KB
- references/debt-frameworks.md 14 KB
- references/prioritization-framework.md 11 KB
- references/stakeholder-communication-templates.md 13 KB
- scripts/debt_dashboard.py 40 KB runs code
- scripts/debt_prioritizer.py 34 KB runs code
- scripts/debt_scanner.py 26 KB runs code
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 Changed · -6 tokens per session 38c451c22a75
- 1mo ago Changed · -2 lines c1f606c7a9ed
- 1mo ago Changed · +31 lines · +33 tokens per session 4bb9c0d4f47f
- 1mo ago First seen · 93 lines · 63 tokens per session scan A 61029ba848ac
tech-debt-tracker is a skill published in the GitHub repository Morningstar202604/awesome-skillkit (0 stars, last pushed 25d ago), licensed Apache-2.0. It adds 90 tokens to every session and 1,744 once invoked, about $0.0004 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 89% identical to tech-debt-tracker, differing in 126 lines, and is treated as a copy.
Other skills, from other repositories
otto-pr-review-loop
Run Polly and OCR on a PR until all findings settle.
architecture-review
Review a diff or a branch range for the architecture drift lint cannot see. Run the scoped linters and the parity check first. Then work a checklist keyed to dev/docs/ARCHITECTURE.md: new Api operations or contract shapes without a ruling, new or cut edges between modules, authorization or audit hand-rolled beside the…
meta-codereview-current-diff
Read the current uncommitted diff, run three independent reviewers (safety + tests-coverage + style) in parallel, then arbitrate a single BLOCK / BLOCKWITHOVERRIDE / PASSWITHNOTES verdict. Use before commit when you want a multi-perspective second-opinion instead of a single-reviewer agent loop.
prs-awaiting-maintainer
List open pull requests where the ball is in the maintainer's court: CI is green and the PR is ready for a maintainer to review, re-review, or merge. Use when the user wants to see PRs awaiting maintainer action.
compliance-checker
Check affiliate content for FTC compliance and platform rules. Triggers on: "check my content for compliance", "FTC disclosure check", "is this legal", "review for compliance", "check affiliate disclosure", "am I FTC compliant", "audit my content", "compliance review", "legal check", "platform rules check", "check…
review-pr
Review a pull request for code quality and security issues. Use when the user wants to review a PR, check PR code changes, or audit a pull request. Triggers on: "review PR", "review pull request", "check this PR", "the review-pr skill".