A codebase assessment tool that finds and organizes technical debt: unfinished work, workarounds, duplication, overly large files or functions, and outdated code markers.

Use it to scan a project, add debt items, reorder them by importance, and produce a status summary.

It turns scattered maintenance problems into a register that can be categorized, prioritized, and reported instead of being forgotten.

tech-debt — Skill for Claude Code by HolyMonkey

Install

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.

Any agent

npx skills add HolyMonkey/youtube-example-ai-studio --skill tech-debt

Clone the repo

git clone --depth 1 https://github.com/HolyMonkey/youtube-example-ai-studio

Made for: Claude Code.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/holymonkey/youtube-example-ai-studio/tech-debt.svg)](https://agentmods.dev/skills/holymonkey/youtube-example-ai-studio/tech-debt)

Your own site

<a href="https://agentmods.dev/skills/holymonkey/youtube-example-ai-studio/tech-debt"><img src="https://agentmods.dev/badge/skills/holymonkey/youtube-example-ai-studio/tech-debt.svg" alt="Measured on agentmods" height="20"></a>

Per session 33 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 776 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin 100% copy Near-identical to another mod in the catalogue.

Token cost

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.00033	$0.00776
Opus 5	$0.00016	$0.00388
Sonnet 5	$0.00007	$0.00155
Haiku 4.5	$0.00003	$0.00078

Measured 4d ago against content hash 506b3525d34d, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, from the pricing page.

Security

Grade A, and why

tech-debt 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 4d 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.

Origin

This is a copy

100% identical to tech-debt — 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.

.claude/skills/tech-debt/SKILL.md · 71 lines

How it starts

The opening of the file, as written. The whole thing — 71 lines — stays where its author put it; the contents beside it link to each section on GitHub.

When this skill is invoked:

Parse the subcommand from the argument:
- scan — Scan the codebase for tech debt indicators
- add — Add a new tech debt entry manually
- prioritize — Re-prioritize the existing debt register
- report — Generate a summary report of current debt status
For scan:
- Search the codebase for debt indicators:
  - TODO comments (count and categorize)
  - FIXME comments (these are bugs disguised as debt)
  - HACK comments (workarounds that need proper solutions)
  - @deprecated markers
  - Duplicated code blocks (similar patterns in multiple files)
  - Files over 500 lines (potential god objects)
  - Functions over 50 lines (potential complexity)
- Categorize each finding:
  - Architecture Debt: Wrong abstractions, missing patterns, coupling issues
  - Code Quality Debt: Duplication, complexity, naming, missing types
  - Test Debt: Missing tests, flaky tests, untested edge cases
  - Documentation Debt: Missing docs, outdated docs, undocumented APIs
  - Dependency Debt: Outdated packages, deprecated APIs, version conflicts
  - Performance Debt: Known slow paths, unoptimized queries, memory issues
- Update the debt register at docs/tech-debt-register.md
For add:
- Prompt for: description, category, affected files, estimated fix effort, impact if left unfixed
- Append to the debt register
For prioritize:
- Read the debt register
- Score each item by: (impact_if_unfixed * frequency_of_encounter) / fix_effort
- Re-sort the register by priority score
- Recommend which items to include in the next sprint
For report:
- Read the debt register
- Generate summary statistics:
  - Total items by category
  - Total estimated fix effort
  - Items added vs resolved since last report
  - Trending direction (growing / stable / shrinking)
- Flag any items that have been in the register for more than 3 sprints
- Output the report

Debt Register Format

## Technical Debt Register
Last updated: [Date]
Total items: [N] | Estimated total effort: [T-shirt sizes summed]

| ID | Category | Description | Files | Effort | Impact | Priority | Added | Sprint |
|----|----------|-------------|-------|--------|--------|----------|-------|--------|
| TD-001 | [Cat] | [Description] | [files] | [S/M/L/XL] | [Low/Med/High/Critical] | [Score] | [Date] | [Sprint to fix or "Backlog"] |

Read the full file on GitHub · 71 lines

Changes

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.

4d ago First seen · 71 lines · 33 tokens per session scan A 506b3525d34d

Subscribe to this mod's changes

tech-debt is a skill published in the GitHub repository HolyMonkey/youtube-example-ai-studio (11 stars, last pushed 5mo ago), licensed MIT. It adds 33 tokens to every session and 776 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to tech-debt, differing in 0 lines, and is treated as a copy.

Code review Planning

autoreview

Pre-commit/ship code review: Codex default; optional Claude or Pi.

openclaw/clawhub · 20 tokens

rework-rate

Measure and interpret PR rework rate — the emerging 5th DORA metric.

bradygaster/squad · 20 tokens

omh-code-review

This is a Hermes-native code-review workflow skill.

rlaope/oh-my-hermes · 46 tokens

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"…

umputun/revdiff · 84 tokens

code-reviewer

Code review specialist focused on patterns, bugs, security, and performance.

RightNow-AI/openfang · 17 tokens

agent-teams-simplify-and-harden

Implementation + audit loop using parallel agent teams with structured simplify, harden, and document passes. Spawns implementation agents to do the work, then audit agents to find complexity, security gaps, and spec deviations, then loops until code compiles cleanly, all tests pass, and auditors find zero issues or…

LeoYeAI/openclaw-master-skills · 115 tokens