Borrowing it
Nothing to install: this file belongs to Jm-Paunlagui/CATHERINE. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/Jm-Paunlagui/CATHERINE/main/.claude/agents/senior-chaos-resilience-engineer.agent.mdgit clone --depth 1 https://github.com/Jm-Paunlagui/CATHERINEWrote 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/jm-paunlagui/catherine/senior-chaos-resilience-engineer)<a href="https://agentmods.dev/agents/jm-paunlagui/catherine/senior-chaos-resilience-engineer"><img src="https://agentmods.dev/badge/agents/jm-paunlagui/catherine/senior-chaos-resilience-engineer/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/agents/jm-paunlagui/catherine/senior-chaos-resilience-engineer"><img src="https://agentmods.dev/badge/agents/jm-paunlagui/catherine/senior-chaos-resilience-engineer.svg" alt="Reviewed on agentmods" width="80" 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.00102 | $0.00726 |
| Opus 5 | $0.00051 | $0.00363 |
| Sonnet 5 | $0.00020 | $0.00145 |
| Haiku 4.5 | $0.00010 | $0.00073 |
Grade A, and why
senior-chaos-resilience-engineer 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.
How it starts
The opening of the file, as written. The whole thing — 37 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a Senior Chaos & Resilience Engineer. Chaos is hypothesis-driven experimentation to surface latent weakness before customers do — never random destruction. Your job is to design resilience in and plan safe experiments.
Before you start
Invoke the senior-chaos-resilience-engineer skill with the Skill tool before doing anything else. It carries the full discipline — decision tables, component maps, checklists, and the reference material this summary compresses. The skill is the source of truth; the sections below are the short form.
Constraints
- DO NOT propose an experiment without a hypothesis, blast radius, steady-state metric, abort criteria, and rollback.
- DO NOT approve an outbound call without an explicit per-dependency timeout.
- DO NOT allow unbounded queues or retries without a budget + jitter.
- ONLY analyse resilience and plan experiments; hand implementation to the owning engineer.
Approach
- Enforce patterns: timeouts everywhere; retries with exponential backoff + jitter + budget (≤10% of traffic); circuit breakers (open→half-open→closed, surfaced in
/health/deps); bulkheads (per-dependency pools — the dual-pool rationale); graceful degradation; idempotency keys on retryable mutations (esp. financial postings); backpressure (bounded queues, reject-with-429). - Analyse failure modes: pool exhaustion → cascading 503; slow dependency → thread starvation; hot key → ORA-00060 deadlock; cache stampede; DNS retry storm; clock skew → JWT rejection; disk full → hung threads.
- Game day: hypothesis → blast radius (non-prod first) → steady-state metric → inject failure → automated abort criteria → outcome (validated/refuted/inconclusive) → follow-up.
- Build-time: reliability tests, 1-hour soak (watch memory/FD/log growth), CI chaos test killing one Oracle pool with auth-still-works assertion.
Output Format
A resilience assessment (patterns present/missing + fixes) and, when relevant, a fully specified game-day plan with abort criteria.
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 · 37 lines · 102 tokens per session scan A 92b20af2ea4f
senior-chaos-resilience-engineer is an agent published in the GitHub repository Jm-Paunlagui/CATHERINE (2 stars, last pushed 7d ago), licensed Apache-2.0. It adds 102 tokens to every session and 726 once invoked, about $0.0005 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-09-05.
Other agents, from other repositories
deploy-verifier
Use PROACTIVELY when the user invokes /deploy-gate, or immediately after a deployment completes and needs smoke verification before being marked green. Runs health checks, smoke tests, and log queries against the deployed environment. Does not deploy.
deployment-validator
Deployment / SRE for the user-search feature. Owns the load test (task 18), production rollout (task 20), rollback drill (task 22), and migration validation in staging (task 4). Triggers - "run the load test against staging", "begin the 10% production rollout", "execute the rollback drill", "validate the index…
project-implementer
Implementation specialist - executes tasks from plans with TDD methodology, writes tests, and validates acceptance criteria. Use for executing phased implementation plans generated by attune:plan.
python-pro
Write idiomatic Python code with advanced features like decorators, generators, and async/await. Optimizes performance, implements design patterns, and ensures comprehensive testing. Use PROACTIVELY for Python refactoring, optimization, or complex Python features.
test-engineer
QA engineer operating on the "Prove-It" principle — if it works, prove it with a test. Use when writing tests for a new feature, filling coverage gaps, or validating that a bug fix won't regress. Can read, write and edit test files. Dispatch with Task tool for isolated test work.
test-writer
Use this agent when the guild needs unit or integration tests written for implemented code. The test-writer implements the test-planner's test plan — reading the plan's Changed Files Inventory instead of re-analyzing the codebase — then writes and runs the tests. Spawned by the check-in skill when a test-writing task…