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 agentmods add skills/vm0-ai/vm0/tech-debtnpx skills add vm0-ai/vm0 --skill tech-debtgit clone --depth 1 https://github.com/vm0-ai/vm0Wrote 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/vm0-ai/vm0/tech-debt)<a href="https://agentmods.dev/skills/vm0-ai/vm0/tech-debt"><img src="https://agentmods.dev/badge/skills/vm0-ai/vm0/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 | $0.00018 | $0.07142 |
| Opus 5 | $0.00009 | $0.03571 |
| Sonnet 5 | $0.00004 | $0.01428 |
| Haiku 4.5 | $0.00002 | $0.00714 |
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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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 · 886 lines · 18 tokens per session scan A 846797a54868
tech-debt is a skill published in the GitHub repository vm0-ai/vm0 (1,154 stars, last pushed today), with no licence file. It adds 18 tokens to every session and 7,142 once invoked, about $0.0001 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
h5i
Use when browsing the web or a local app on behalf of a user, or when work should run inside a disposable, confined development box instead of on the host — opening a browser session and reading a page as an outline with @ref handles, auditing what that session actually reached, reviewing a pull request or any…
QA Review Templates
Sidecar data for /qa workflow — Red Team personas, dimension checklists, and QA report templates loaded just-in-time.
deep-reasoning
Structured Chain-of-Thought (CoT) & Deep Reasoning Protocol for complex problem analysis, architectural decisions, security evaluations, and deep troubleshooting. Activate when --deep or --cot flag is present in workflows, or when deep architectural reasoning is required. Supports MCP Graph integration for…
Plan Templates
Sidecar data for /plan workflow — Detail Plan and Roadmap templates loaded just-in-time.
scan-sec
Use when scanning code for security vulnerabilities. Use when user says "scan security", "kiểm tra bảo mật", "security audit", "review security", or invokes /scan-sec. For large scans (>20 main-language files OR >30 total OR >14 days) processes chunks sequentially. Outputs bilingual reports (vi/en).
spec-driven-development
Governance skill for /spec workflow — provides spec templates, assumption surfacing rules, boundary definitions, and quality checklists. Load when creating specifications, defining feature scope, surfacing assumptions, writing acceptance criteria, or reviewing specs. Even if the user doesn't mention "spec", load this…