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 dungnotnull/hybrid-harness-chaos-process-prm --skill s26-resilience-scoringgit clone --depth 1 https://github.com/dungnotnull/hybrid-harness-chaos-process-prmWrote 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/dungnotnull/hybrid-harness-chaos-process-prm/s26-resilience-scoring)<a href="https://agentmods.dev/skills/dungnotnull/hybrid-harness-chaos-process-prm/s26-resilience-scoring"><img src="https://agentmods.dev/badge/skills/dungnotnull/hybrid-harness-chaos-process-prm/s26-resilience-scoring/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/dungnotnull/hybrid-harness-chaos-process-prm/s26-resilience-scoring"><img src="https://agentmods.dev/badge/skills/dungnotnull/hybrid-harness-chaos-process-prm/s26-resilience-scoring.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.00089 | $0.03203 |
| Opus 5 | $0.00044 | $0.01602 |
| Sonnet 5 | $0.00018 | $0.00641 |
| Haiku 4.5 | $0.00009 | $0.00320 |
Grade A, and why
chaos-resilience-scoring 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 12d 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 — 373 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Resilience Scoring (s24)
Purpose
Provide a quantitative, repeatable framework for measuring system resilience — transforming subjective "we think it's resilient" into objective scores that can be tracked over time, compared across services, and used as gates for production promotion.
Prerequisites
- Security scan results from s11
- Test results from s12 (E2E testing)
- Chaos experiment results from s14-s19
- [ | Observability data from s22
- Policy governance from s24
- Alert recommendations from s23
Input Contract
| Input | Source | Required |
|---|---|---|
| All experiment results | s12-s18 outputs | Yes |
| Game day results report | s18 output | Yes |
| Observability data (error rates, latency) | s20 output | Yes |
| Post-chaos test evidence | s11 (rerun) | Yes |
| Cost impact data | s23 output | No |
| Recommendations | s21 output | Yes |
| Previous resilience scores (trend) | Previous s24 runs | No |
Output Contract
| Output | Destination | Format |
|---|---|---|
| Resilience score card per service | .commandcode/artifacts/resilience-<service>.json |
JSON |
| Platform resilience report | .commandcode/artifacts/platform-resilience-report.md |
Markdown |
| Resilience trend data | s25 (postmortem) | JSON (array) |
| Production promotion gate | s22 (governance) | Boolean + score |
| Service maturity matrix | s25 (improvement roadmap) | Table |
Resilience Scoring Formula
Resilience Score = Σ(Component Scores × Weights) × Coverage Factor
Where:
Component Scores (0-100 each):
Availability Score — How well did the service stay available?
Performance Score — How well did performance hold up?
Recovery Score — How fast did the service recover?
Correctness Score — Did the service behave correctly?
Observability Score — Could we see what was happening?
Weights (sum to 1.0):
Availability: 0.30
Performance: 0.20
Recovery: 0.20
Correctness: 0.15
Observability: 0.15
Coverage Factor (0.0-1.0):
= Experiments_Run / Experiments_Planned
(penalizes services that skip experiments)
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.
- 12d ago First seen · 373 lines · 89 tokens per session scan A 06408d5af496
chaos-resilience-scoring is a skill published in the GitHub repository dungnotnull/hybrid-harness-chaos-process-prm (19 stars, last pushed 3mo ago), licensed MIT. It adds 89 tokens to every session and 3,203 once invoked, about $0.0004 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…