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 s19-application-faultsgit 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/s19-application-faults)<a href="https://agentmods.dev/skills/dungnotnull/hybrid-harness-chaos-process-prm/s19-application-faults"><img src="https://agentmods.dev/badge/skills/dungnotnull/hybrid-harness-chaos-process-prm/s19-application-faults/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/s19-application-faults"><img src="https://agentmods.dev/badge/skills/dungnotnull/hybrid-harness-chaos-process-prm/s19-application-faults.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.00094 | $0.03558 |
| Opus 5 | $0.00047 | $0.01779 |
| Sonnet 5 | $0.00019 | $0.00712 |
| Haiku 4.5 | $0.00009 | $0.00356 |
Grade A, and why
chaos-application-faults scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
# Verify: curl -w "\nTotal time: %{time_total}s\n" http://<SERVICE_A>/health How it starts
The opening of the file, as written. The whole thing — 499 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Chaos Application Faults (s17)
Purpose
Produce complete, safe, runnable application-level chaos experiments that test service resilience against pod failures, container crashes, network degradation, DNS misconfiguration, and dependency timeouts.
Prerequisites
- Chaos experiment designs from s14 (Experiment Design)
- Target application deployed and accessible
- Steady state defined from s17 (Steady State)
- Blast radius approved from s16 (Blast Radius Control)
- Observability active and monitoring application metrics
Input Contract
| Input | Source | Required |
|---|---|---|
| Experiment design framework | s12 (workflow_context.artifacts) | Yes |
| Service definitions + pod labels | s05 output | Yes |
| Blast radius constraints | s14 output | Yes |
| Steady state probes | s15 output | Yes |
| Risk tolerance preferences | s02 taste (risk_tolerance) | Yes |
Output Contract
| Output | Destination | Format |
|---|---|---|
| App fault ChaosExperiments | .commandcode/artifacts/experiment-app-<fault>.yaml |
Litmus YAML |
| App fault ChaosEngines | .commandcode/artifacts/engine-app-<fault>.yaml |
Litmus YAML |
| Network fault configurations | .commandcode/artifacts/experiment-network-<fault>.yaml |
Litmus YAML |
| Recovery runbook | s18 (game day), s25 (postmortem) | Markdown |
Application Fault Catalog
| Fault | LitmusChaos Name | Risk | Scope | Prod Safe? |
|---|---|---|---|---|
| Pod Delete | pod-delete | Low | Namespaced | Yes (≤30%) |
| Pod CPU Hog | pod-cpu-hog | Low | Namespaced | Yes (≤30%) |
| Pod Memory Hog | pod-memory-hog | Medium | Namespaced | Yes (≤30%) |
| Container Kill | container-kill | Medium | Namespaced | Yes (≤30%) |
| Pod HTTP Latency | pod-http-latency | Low | Namespaced | Yes |
| Pod Network Loss | pod-network-loss | High | Namespaced | With approval |
| Pod Network Latency | pod-network-latency | Medium | Namespaced | Yes |
| Pod DNS Error | pod-dns-error | Medium | Namespaced | With approval |
| Pod DNS Spoof | pod-dns-spoof | High | Namespaced | No (staging only) |
| Pod IO Stress | pod-io-stress | Medium | Namespaced | With approval |
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 · 499 lines · 94 tokens per session scan A d73b4bf48d6d
chaos-application-faults is a skill published in the GitHub repository dungnotnull/hybrid-harness-chaos-process-prm (19 stars, last pushed 3mo ago), licensed MIT. It adds 94 tokens to every session and 3,558 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
research-engineer
An uncompromising Academic Research Engineer. Operates with absolute scientific rigor, objective criticism, and zero flair. Focuses on theoretical correctness, formal verification, and optimal implementation across any required technology.
tika-eval-compare
Compare extracts from two Tika builds over a corpus to detect regressions in content, encoding, exceptions, and embedded-document handling. Use for "compare before/after extracts", "eval this change against the corpus".
neuron-evaluation-engineer
Create and run AI evaluations with datasets, assertions, and output drivers in Neuron AI. Use this skill whenever the user mentions evaluation, testing AI systems, creating evaluators, dataset-driven testing, assertion-based validation, or wants to measure AI system performance. Also trigger for tasks involving…
jetson-validate-image
Use after jetson-flash-image to run static BSP checks, on-target smoke/regression tests on a flashed DUT, or both. Not for build or flash steps. Triggers: validate bsp, on-target validation.
atmos-validation
Validate Atmos projects, components, arbitrary JSON Schema inputs, EditorConfig, and GitHub Actions; use affected-file selection and native CI annotations.
skill-benchmark
Benchmark AI skill effectiveness by measuring implementation quality against legacy constraints.