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 commands/vedanta/the-system/ts-validate-docsgit clone --depth 1 https://github.com/vedanta/the-systemWrote 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/vedanta/the-system/ts-validate-docs)<a href="https://agentmods.dev/commands/vedanta/the-system/ts-validate-docs"><img src="https://agentmods.dev/badge/commands/vedanta/the-system/ts-validate-docs.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.00000 | $0.01770 |
| Opus 5 | $0.00000 | $0.00885 |
| Sonnet 5 | $0.00000 | $0.00354 |
| Haiku 4.5 | $0.00000 | $0.00177 |
Grade B, and why
ts-validate-docs scanned grade B with 1 finding 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 2d 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
grep -q "Override Flags: --docs=lean" .claude/pipeline/projects/test-app.md The source is not reproduced here
Licensed LGPL-3.0
The repository is licensed LGPL-3.0, which this catalogue does not treat as permission to reproduce the file. Read it at the source.
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.
- 2d ago First seen · 245 lines · 0 tokens per session scan B 7644754e805f
ts-validate-docs is a command published in the GitHub repository vedanta/the-system (9 stars, last pushed 6mo ago), licensed LGPL-3.0. It costs nothing until one of its globs matches a file; then it loads 1,770 tokens. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other commands, from other repositories
self-healing
Automatically detect and recover from errors without interrupting your flow.
pr-enhance
Command "pr-enhance" from ruvnet/ruflo, covering pr-enhance, usage, options, examples and enhance pr.
repo-architect
Repository structure optimization and multi-repo management with ruv-swarm coordination for scalable project architecture and development workflows.
auto-verify
프론트엔드 UX 검증 — Playwright 기반 비주얼 검증을 실행합니다.
fix-bug
Systematically reproduce, isolate, fix, test, and document a bug.
nio
Nio — scan code, evaluate an action, read the audit report, manage config.