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 paruff/uFawkesAI --skill e2e-failure-pathsgit clone --depth 1 https://github.com/paruff/uFawkesAIWrote 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/paruff/ufawkesai/e2e-failure-paths)<a href="https://agentmods.dev/skills/paruff/ufawkesai/e2e-failure-paths"><img src="https://agentmods.dev/badge/skills/paruff/ufawkesai/e2e-failure-paths/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/paruff/ufawkesai/e2e-failure-paths"><img src="https://agentmods.dev/badge/skills/paruff/ufawkesai/e2e-failure-paths.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.00041 | $0.00534 |
| Opus 5 | $0.00020 | $0.00267 |
| Sonnet 5 | $0.00008 | $0.00107 |
| Haiku 4.5 | $0.00004 | $0.00053 |
Grade A, and why
e2e-failure-paths 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 9d 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
Skill: E2E Failure Path Testing
Load trigger:
"load e2e-failure-paths skill"> DORA: Cap 5 (Operational Resilience) Token cost: Low
Purpose
Validate pipeline behavior under failure conditions.
Responsibilities
- Simulate test failures
- Simulate SAST failures
- Simulate build failures
- Validate no GitOps update occurs
- Validate correct error propagation
Inputs
- Failure scenarios
Outputs
e2e-failure.json
Sub-Skills
| Skill | Purpose |
|---|---|
e2e-failure-paths/pipeline-failures |
Negative pipeline scenarios |
e2e-failure-paths/manifest-protection |
Invalid manifest protection |
Failure Scenarios
| Scenario | Expected Behavior |
|---|---|
| Unit test failure | Pipeline stops, no GitOps update |
| Integration test failure | Pipeline stops, no GitOps update |
| SAST failure | Pipeline stops, no GitOps update |
| Build failure | Pipeline stops, no GitOps update |
| Invalid manifest | Pipeline stops, no GitOps update |
Validation Rules
- No invalid GitOps updates
- Correct failure behavior
- Error propagation correct
- Pipeline stops cleanly
Output Format
{
"skill": "e2e-failure-paths",
"status": "pass | fail",
"scenarios": {
"unit_test_failure": { "stopped": true, "gitops_update": false },
"sast_failure": { "stopped": true, "gitops_update": false },
"build_failure": { "stopped": true, "gitops_update": false },
"invalid_manifest": { "stopped": true, "gitops_update": false }
},
"total_scenarios": 4,
"all_correct": true
}
Success Criteria
- No invalid GitOps updates
- Correct failure behavior
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 9d ago First seen · 81 lines · 41 tokens per session scan A 735ecfeee432
e2e-failure-paths is a skill published in the GitHub repository paruff/uFawkesAI (2 stars, last pushed 16d ago), licensed MIT. It adds 41 tokens to every session and 534 once invoked, about $0.0002 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-31.
Other skills, from other repositories
Checkly Monitoring as Code
Teach agents to build synthetic monitoring as code with Checkly, including Playwright browser checks, API checks, alerting, and CI deploy workflows.
CI Test Sharding Parallelization
Teach agents to shard and parallelize Playwright, Jest, and pytest suites in CI to reduce wall-clock time while merging reports reliably.
CI/CD Pipeline Config
CI/CD pipeline configuration skill for test automation, covering GitHub Actions, Jenkins, GitLab CI, test parallelization, reporting, and artifact management.
setup-guardrails
Stand up continuous guardrails on Stunt Double — checklists for critical user flows plus a workflow that re-runs them on a schedule or on deploy/PR events, so regressions surface before users do.
Ephemeral Environment Testing
Testing in ephemeral preview environments for pull requests including environment provisioning, data seeding, and automated teardown.
Desktop Application Testing
Testing desktop applications built with Electron, Tauri, or native frameworks including window management, IPC, tray icons, and auto-update testing.