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 arbazkhan971/godmode --skill chaosgit clone --depth 1 https://github.com/arbazkhan971/godmodeWrote 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/arbazkhan971/godmode/chaos)<a href="https://agentmods.dev/skills/arbazkhan971/godmode/chaos"><img src="https://agentmods.dev/badge/skills/arbazkhan971/godmode/chaos/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/arbazkhan971/godmode/chaos"><img src="https://agentmods.dev/badge/skills/arbazkhan971/godmode/chaos.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00024 | $0.02477 |
| Opus 5 | $0.00012 | $0.01239 |
| Sonnet 5 | $0.00005 | $0.00495 |
| Haiku 4.5 | $0.00002 | $0.00248 |
Grade A, and why
chaos 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 — 307 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Chaos — Chaos Engineering
Activate When
- User invokes
/godmode:chaos - User says "chaos test", "resilience test", "failure injection", "break it on purpose"
- User asks "what happens when X fails?" or "is this resilient?"
- User wants to plan a game day or disaster recovery drill
- Ship skill needs resilience validation before production deployment
- After a production incident, to prevent recurrence
Workflow
Step 1: Define Steady State
Before injecting failures, establish what "healthy" looks like:
STEADY STATE DEFINITION:
System: <service name / system boundary>
Architecture: <monolith | microservices | serverless>
Health indicators (must all be true for "steady state"):
- Response success rate: > <X>% (e.g., 99.9%)
- Response time P95: < <X>ms (e.g., 500ms)
- Error rate: < <X>% (e.g., 0.1%)
- Queue depth: < <N> messages (e.g., 1000)
- CPU usage: < <X>% (e.g., 80%)
- Memory usage: < <X>% (e.g., 85%)
- Active connections: < <N> (e.g., connection pool max)
...
Step 2: Identify Failure Domains
Map all the ways the system can fail:
FAILURE DOMAIN MAP:
| Category | Components | Impact if Failed |
|--|--|--|
| Network | Load balancer | Total outage |
| | DNS resolution | Total outage |
| | Inter-service network | Partial outage |
| | External API access | Feature degraded |
| Compute | Application process | Service restart |
| | Worker processes | Queue backlog |
| | Cron/scheduled jobs | Delayed tasks |
| | Container/VM host | Service relocation |
| Storage | Primary database | Read/write loss |
IF experiment crashes service: halt and rollback. WHEN steady-state violated: record finding.
Step 3: Design Chaos Experiments
Create specific, controlled experiments for each failure domain:
Experiment Template
CHAOS EXPERIMENT:
Name: <descriptive name>
Hypothesis: "When <failure condition>, the system will <expected behavior>"
Blast radius: <single request | single user | single service | entire system>
Duration: <how long to inject failure>
Rollback: <how to stop the experiment immediately>
Prerequisites:
- [ ] Steady state verified
- [ ] Monitoring dashboards open
- [ ] Rollback procedure tested
- [ ] Team notified (if production)
- [ ] Incident response team on standby (if production)
...
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 · 307 lines · 24 tokens per session scan A 9203a0137b1b
chaos is a skill published in the GitHub repository arbazkhan971/godmode (26 stars, last pushed 12d ago), licensed MIT. It adds 24 tokens to every session and 2,477 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
asc-shots-pipeline
Orchestrate iOS screenshot automation with xcodebuild/simctl for build-run, AXe for UI actions, JSON settings and plan files, Koubou-based framing (asc screenshots frame), and screenshot upload (asc screenshots upload). Use when users ask for automated screenshot capture, AXe-driven simulator flows, frame composition…
dev-branch-deploy
Drive the Hermes/Maia Concourse dev-branch deploy workflow — test stack changes in a live lab before merging to master. Use for "dev branch", "deploy to dev", "hermes-dev-branch", "maia-dev-branch", "test in labs", "dev lane". Covers both the hermes and maia stacks.
ap-implementer
L3 executor - G4 IMPLEMENT. Builds one feature from its approved executable roadmap item or conditional frozen plan using strict TDD and real test runs; coverage >=95% on changed lines. Reports PLAN-CONFLICT rather than improvising.
qa-manual-istqb
Create QA artifacts from requirements: test plans, test conditions/cases, bug reports, regression suites, traceability, and exploratory charters. Use for test planning, test design, defects, coverage, or QA deliverables. Applies ISTQB risk-based techniques and loads templates only when needed. Keywords: test plan…
testing-patterns
Testing strategy: pyramid, AAA, mocks/fakes/stubs, flaky tests, coverage. Triggers: test, fixture, mock, stub, e2e, TDD, Playwright, Cypress, flaky, coverage, property-based.
broken-access-control
Replay captured requests with swapped identities and bumped object IDs to surface broken access control. Use when testing for IDOR or authz flaws.