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.
git clone --depth 1 https://github.com/nolabs-ai/claude-extensionsWrote 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/commands/nolabs-ai/claude-extensions/tech-debt)<a href="https://agentmods.dev/commands/nolabs-ai/claude-extensions/tech-debt"><img src="https://agentmods.dev/badge/commands/nolabs-ai/claude-extensions/tech-debt.svg" alt="Measured on agentmods" 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.00009 | $0.00570 |
| Opus 5 | $0.00005 | $0.00285 |
| Sonnet 5 | $0.00002 | $0.00114 |
| Haiku 4.5 | $0.00001 | $0.00057 |
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 6d 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 — 99 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Technical Debt Analysis
Scan the codebase to identify and catalog technical debt, including TODOs, FIXMEs, deprecated code, and code quality issues.
Process
-
Find Explicit Markers
grep -rn "TODO\|FIXME\|HACK\|XXX\|BUG\|DEPRECATED" src/ -
Analyze Code Quality
- Check for large files (>500 lines)
- Find complex functions (high cyclomatic complexity)
- Identify duplicated code
- Look for outdated patterns
-
Check Dependencies
- Find deprecated dependencies
- Identify outdated major versions
- Look for security advisories
-
Review Documentation
- Missing documentation
- Outdated documentation
- Incomplete API docs
Output Format
Technical Debt Summary
| Category | Count | Priority |
|---|---|---|
| TODOs | 15 | Medium |
| FIXMEs | 3 | High |
| Deprecated Code | 5 | Medium |
| Large Files | 8 | Low |
Explicit Markers
High Priority (FIXME/BUG)
| File | Line | Comment |
|---|---|---|
| src/auth.js | 42 | FIXME: Race condition in token refresh |
| src/api.js | 156 | BUG: Doesn't handle network errors |
Medium Priority (TODO)
| File | Line | Comment |
|---|---|---|
| src/utils.js | 23 | TODO: Add input validation |
Code Quality Issues
Large Files (>500 lines)
| File | Lines | Suggestion |
|---|---|---|
| src/UserService.js | 850 | Split into smaller modules |
Complex Functions
| Function | File | Complexity | Suggestion |
|---|---|---|---|
| processOrder | orders.js | High | Extract sub-functions |
Deprecated Dependencies
| Package | Current | Status | Action |
|---|---|---|---|
| moment | 2.29.0 | Deprecated | Migrate to date-fns or dayjs |
Recommended Actions
Immediate
- Fix FIXME items (security/correctness)
- Update deprecated dependencies
Short-term
- Address TODO items
- Refactor large files
Long-term
- Reduce code duplication
- Improve documentation coverage
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.
- 6d ago First seen · 99 lines · 9 tokens per session scan A a1ae55e2e60e
tech-debt is a command published in the GitHub repository nolabs-ai/claude-extensions (5 stars, last pushed 8mo ago), licensed MIT. It adds 9 tokens to every session and 570 once invoked, about $0.0000 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 commands, from other repositories
sdd-init
Initialize SDD context — detects project stack and bootstraps persistence backend.
review-branch
Review the current branch's diff against base by dispatching atomic-reviewer. No orchestration loop, no spec required — pre-flight before /commit pr or /commit merge.
init
Install the formatters this repository needs, with every command visible before it runs.
review-sdk-app
Review and validate a Claude Agent SDK application against best practices.
repo-audit
Audit a codebase (local or remote GitHub/GitLab) against architecture principles and requirements, surfacing drift, risk, and missing decisions.
security-review
AI-powered security review of the current git diff (or specified paths). Dispatches the security-reviewer agent and prints findings grouped by severity.