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-incidentgit 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-incident)<a href="https://agentmods.dev/commands/vedanta/the-system/ts-incident"><img src="https://agentmods.dev/badge/commands/vedanta/the-system/ts-incident.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.02042 |
| Opus 5 | $0.00000 | $0.01021 |
| Sonnet 5 | $0.00000 | $0.00408 |
| Haiku 4.5 | $0.00000 | $0.00204 |
Grade A, and why
ts-incident 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.
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.
- 6d ago First seen · 254 lines · 0 tokens per session scan A 734ce94a351e
ts-incident 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 2,042 tokens. 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
self-healing
Automatically detect and recover from errors without interrupting your flow.
doctor
Health-check the harness: kernel load, MCP wiring, memory backend, host adapter.
init
This tool coordinates Claude Code's actions. It does NOT write code or create content.
refactor-clean
You are a code refactoring expert specializing in clean code principles, SOLID design patterns, and modern software engineering best practices. Analyze and refactor the provided code to improve its quality, maintainability, and performance.
service-check
Request each agent to run a self-diagnostic to validate their runtime setup.
fix
Auto-detect and fix LSP errors, linting issues, and type errors.