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 AsyrafHussin/agent-skills --skill technical-debtgit clone --depth 1 https://github.com/AsyrafHussin/agent-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/asyrafhussin/agent-skills/technical-debt)<a href="https://agentmods.dev/skills/asyrafhussin/agent-skills/technical-debt"><img src="https://agentmods.dev/badge/skills/asyrafhussin/agent-skills/technical-debt/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/asyrafhussin/agent-skills/technical-debt"><img src="https://agentmods.dev/badge/skills/asyrafhussin/agent-skills/technical-debt.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Socket pass
- Snyk pass
- NVIDIA SkillSpector warn
SkillSpector: 3 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium MCP Rug Pull · line 283 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 284 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 285 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
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.00109 | $0.03582 |
| Opus 5 | $0.00055 | $0.01791 |
| Sonnet 5 | $0.00022 | $0.00716 |
| Haiku 4.5 | $0.00011 | $0.00358 |
Grade A, and why
technical-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 10d 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 — 322 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Technical Debt
Technical debt audit and prioritization framework for PHP/Laravel (MySQL) and Node/TypeScript/React projects. Contains 42 rules across 10 categories covering code, security, design, dependency, test, performance, data, documentation, infrastructure, and process debt. Produces a ranked ledger (effort × impact) so teams know what to fix first, not just what's broken. Supports both coding reference and audit mode with PASS/FAIL/N/A output.
Metadata
- Version: 1.0.0
- Scope: PHP / Laravel (MySQL) + Node / TypeScript / React
- Rule Count: 42 rules across 10 categories
- License: MIT
How to Audit
When the user asks to "audit technical debt", "find tech debt", or "what should we refactor first" — run the checklist below against their codebase and produce a ranked debt ledger.
Audit Step 1: Determine Scope
- If arguments provided (
$ARGUMENTS): audit only those paths or modules - If no arguments: audit the entire repository starting from the root
Audit Step 2: Detect Project Stack
Inspect composer.json and package.json to determine which of the supported stacks (PHP/Laravel, Node/TypeScript/React, or both) is in use. Tooling commands (composer outdated, npm outdated, phpstan, eslint, knip, etc.) are chosen based on this detection.
Audit Step 3: Run Debt Checklist
Work through every item below. For each, output:
- PASS — brief confirmation of what was verified
- FAIL — exact
file:line(or command output), description of the debt, effort estimate (S/M/L), and impact (LOW/MED/HIGH/CRITICAL) - N/A — if the check does not apply to this project
Code Debt
- No duplicated blocks > 30 lines across files
- No function exceeds 50 lines or cyclomatic complexity > 10
- No class exceeds 300 lines or has > 15 public methods (god class)
- No unreachable code, unused exports, or commented-out blocks left in source
- No magic numbers or unexplained string literals in business logic
- No function exceeds 4 parameters (use a parameter object)
What ships with it
47 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.
- AGENTS.md 149 KB
- metadata.json 5.3 KB
- README.md 3.2 KB
- rules/_sections.md 3.1 KB
- rules/_template.md 759 B
- rules/code-complexity.md 2.7 KB
- rules/code-dead-code.md 2.8 KB
- rules/code-duplication.md 2.8 KB
- rules/code-god-classes.md 3.3 KB
- rules/code-long-functions.md 3.2 KB
- rules/code-long-parameter-lists.md 3.5 KB
- rules/code-magic-numbers.md 3.6 KB
- rules/data-missing-indexes.md 4.7 KB
- rules/data-orphaned-records.md 5.5 KB
- rules/data-schema-drift.md 4.4 KB
- rules/deps-abandoned-packages.md 3.0 KB
- rules/deps-outdated-versions.md 2.6 KB
- rules/deps-security-advisories.md 2.4 KB
- rules/deps-unused-deps.md 2.4 KB
- rules/design-circular-deps.md 2.4 KB
- rules/design-leaky-abstractions.md 2.9 KB
- rules/design-shotgun-surgery.md 2.8 KB
- rules/design-tight-coupling.md 2.8 KB
- rules/docs-outdated-architecture.md 3.7 KB
- rules/docs-stale-comments.md 3.4 KB
- rules/docs-undocumented-api.md 3.7 KB
- rules/infra-build-warnings.md 3.2 KB
- rules/infra-deprecated-apis.md 3.1 KB
- rules/infra-monitoring-gaps.md 5.9 KB
- rules/infra-runtime-versions.md 3.0 KB
- rules/infra-secrets-management.md 4.3 KB
- rules/perf-bundle-bloat.md 3.7 KB
- rules/perf-missing-pagination.md 3.9 KB
- rules/perf-n-plus-one.md 3.7 KB
- rules/perf-no-caching.md 5.4 KB
- rules/process-debt-tracking.md 3.6 KB
- rules/process-deprecated-markers.md 3.3 KB
- rules/process-feature-flags-lingering.md 5.1 KB
- rules/process-ownership-gaps.md 4.3 KB
- rules/process-todo-fixme-aging.md 3.3 KB
- rules/security-auth-hardening.md 4.8 KB
- rules/security-input-validation.md 4.9 KB
- rules/security-secrets-in-code.md 3.9 KB
- rules/test-coverage-gaps.md 3.2 KB
- rules/test-disabled-tests.md 2.5 KB
- rules/test-flaky-tests.md 3.3 KB
- rules/test-slow-tests.md 3.1 KB
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.
- 10d ago First seen · 322 lines · 109 tokens per session scan A 5f580db50d04
technical-debt is a skill published in the GitHub repository AsyrafHussin/agent-skills (74 stars, last pushed 13d ago), licensed MIT. It adds 109 tokens to every session and 3,582 once invoked, about $0.0005 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-30.
Other skills, from other repositories
code-humanizer
Use when AI-written code needs structural cleanup or when implementing a change under a guard against AI coding slop — duplicated reimplementations of existing helpers, try-import fallbacks, broad exception swallowing, speculative abstraction layers, v2 copies, dead "for future use" code, narrating comments …
slop-code
Slop review and repair for source code, tests, configuration, generated documentation, README files, commit messages and pull request descriptions. Use when someone asks to review generated or agent-written code for quality, asks whether a diff is padded or ceremonial, asks about hallucinated or slopsquatted imports…
slop-cop
Audit, grade, rewrite, and issue funny evidence-backed tickets for generic AI-slop patterns in prose, social posts, UI/design, and code. Use when asked to de-slop writing, humanize AI copy, grade a draft, review a landing page or generated interface, remove vague claims and repetitive rhetoric, inspect AI-written code…
recipe-front-review
Reviews completed frontend implementation for governing-source compliance, scope economy, repository quality, and security, then applies user-approved React corrections.
new-skill
Scaffold a new brooks-lint analysis skill so it passes npm run validate and npm run evals on the first try — generates skills/{name}/SKILL.md (with the mandatory "Do NOT trigger for:" clause and a Process section citing guide step ranges) plus skills/{name}/{name}-guide.md (sequentially numbered steps), then appends…
brooks-sweep
Full-sweep mode: runs a unified analysis across all quality dimensions — code decay, architecture, tech debt, and test quality — then applies fixes directly to the codebase. Safe changes are auto-applied; risky changes are confirmed before execution. Drawing on twelve classic engineering books. Triggers when: user…