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 miptah21/skills --skill tech-debt-trackergit clone --depth 1 https://github.com/miptah21/skillsWrote 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/miptah21/skills/tech-debt-tracker)<a href="https://agentmods.dev/skills/miptah21/skills/tech-debt-tracker"><img src="https://agentmods.dev/badge/skills/miptah21/skills/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/miptah21/skills/tech-debt-tracker"><img src="https://agentmods.dev/badge/skills/miptah21/skills/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.00048 | $0.01346 |
| Opus 5.5 | $0.00019 | $0.00538 |
| Sonnet 5.5 | $0.00010 | $0.00269 |
| Haiku 4.5 | $0.00005 | $0.00135 |
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.
How it starts
The opening of the file, as written. The whole thing — 155 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Tech Debt Tracker
Category: Engineering Process
Overview
Identify, score, prioritize, and track technical debt across a codebase. Provides a systematic framework for making data-driven decisions about debt remediation vs. feature development.
When to Use
- Codebase health assessments
- Sprint planning — allocating debt reduction time
- Before major refactors — understand what to prioritize
- New team member onboarding — "where are the landmines?"
- Quarterly engineering reviews
Debt Classification
Categories
| Category | Signal Patterns | Impact |
|---|---|---|
| Code Debt | TODOs, FIXMEs, complex functions, duplicated code | Development velocity |
| Architecture Debt | Circular deps, god objects, missing abstractions | Scalability, maintainability |
| Test Debt | Low coverage, missing edge cases, flaky tests | Reliability, confidence |
| Dependency Debt | Outdated packages, known CVEs, abandoned deps | Security, compatibility |
| Documentation Debt | Missing docs, outdated READMEs, no architecture docs | Onboarding, knowledge sharing |
| Infrastructure Debt | Manual deployments, no monitoring, missing CI steps | Reliability, velocity |
Severity Scoring
| Score | Level | Criteria |
|---|---|---|
| 1-3 | Low | Cosmetic, doesn't affect functionality |
| 4-6 | Medium | Slows development, increases cognitive load |
| 7-8 | High | Causes bugs, blocks features, hurts reliability |
| 9-10 | Critical | Security risk, data loss potential, system instability |
Scan Workflow
Step 1: Automated Signals
# Count TODO/FIXME/HACK markers
rtk grep -rn "TODO\|FIXME\|HACK\|XXX\|TEMP\|WORKAROUND" src/ --include="*.ts" --include="*.tsx" --include="*.py" | wc -l
# List them with context
rtk grep -rn "TODO\|FIXME\|HACK" src/ --include="*.ts" --include="*.tsx"
# Find long files (>300 lines — potential god objects)
rtk find src/ -name "*.ts" -o -name "*.tsx" | xargs wc -l | sort -rn | head -20
# Find large functions (crude heuristic)
rtk grep -c "function\|=>" src/**/*.ts | sort -t: -k2 -rn | head -20
# Duplicated code (if jscpd available)
rtk bunx jscpd src/ --min-lines 10 --min-tokens 50
# Test coverage
rtk test bun test -- --coverage 2>/dev/null | tail -5
# Outdated dependencies
rtk bun outdated 2>/dev/null
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 · 155 lines · 48 tokens per session scan A eda074bd8f5c
tech-debt-tracker is a skill published in the GitHub repository miptah21/skills (2 stars, last pushed 4mo ago), licensed MIT. It adds 48 tokens to every session and 1,346 once invoked, about $0.0002 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-09-03.
Other skills, from other repositories
autoreview
Structured code review through the shared OpenClaw agent-skills installation.
omh-code-review
This is an OMH code-review workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).
revdiff-plan
Review the last Codex assistant message (plan, analysis, or proposal) with inline annotations in a TUI overlay. Extracts the most recent response from Codex rollout files and opens it in revdiff for review and annotation. Activates on "revdiff-plan", "review plan with revdiff", "annotate plan", "review last response"…
asplos-writing-style
Use when drafting or revising ASPLOS prose — engineering the first two pages that rapid review actually reads, stating the cross-layer insight as one quotable sentence, structuring per-layer mechanism sections, writing bounded claims, and fitting everything into 11 self-contained pages that include figures and…
explore-unknowns
Guide the user through a quadrant walk that maps the unknowns of a task — open by listing the known knowns, then work through known unknowns, unknown knowns, and unknown unknowns one stage at a time, ending with a complete four-quadrant map in the user's hands. Use when a request is ambiguous or underspecified, the…
re0-merge
Review and land an external contribution the way this suite does: gate it against the thesis, land it with the author's credit intact, complete a new skill rather than merging it raw, then approve, credit, and explain before closing. Use when reviewing a pull request, as any collaborator or maintainer, not only the…