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 agents/shafthq/shaft_engine/chaos-enginegit clone --depth 1 https://github.com/ShaftHQ/SHAFT_ENGINEWrote 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/agents/shafthq/shaft_engine/chaos-engine)<a href="https://agentmods.dev/agents/shafthq/shaft_engine/chaos-engine"><img src="https://agentmods.dev/badge/agents/shafthq/shaft_engine/chaos-engine.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.00021 | $0.00069 |
| Opus 5 | $0.00010 | $0.00034 |
| Sonnet 5 | $0.00004 | $0.00014 |
| Haiku 4.5 | $0.00002 | $0.00007 |
Grade A, and why
chaos-engine 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.
What it actually says
Load ChaosEngine, then follow the orchestrator role.
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 · 8 lines · 21 tokens per session scan A bad62b215391
chaos-engine is an agent published in the GitHub repository ShaftHQ/SHAFT_ENGINE (407 stars, last pushed today), licensed MIT. It adds 21 tokens to every session and 69 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 agents, from other repositories
qa
Use this agent when you need to test recent code changes using Playwright automation. Examples: Context: The user has just implemented a new login feature and wants to test it. user: "I just added a new login validation feature, can you test it?" assistant: "I'll use the qa agent to test your recent changes with…
test-engineer
Expert in test strategy, Vitest automation, coverage improvement, quality assurance, integration and E2E testing aligned with Hack23 Secure Development Policy.
golden-fixtures
Captures real Flipper CLI/RPC byte exchanges once and replays them offline in CI, mirroring the workspace VCR-cassette discipline. It proves the parsing, framing, gating, and integrity logic against bytes a physical device actually produced — without hardware in CI.
documcp-test
Write tests for DocuMCP following established patterns.
browser-recorder
Record browser interactions and generate test definitions. Use when: (1) By feature-verify skill after exploration to generate test YAML, (2) By test-authoring skill for assisted test creation, (3) By user for "record this flow" requests.
pr-verifier
Single agent that verifies all PR frontend changes. Use when: (1) verify-pr command is invoked, (2) Complete PR verification with visual report is needed, (3) Running verification in background while user continues working.