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-deployment-validationgit 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-deployment-validation)<a href="https://agentmods.dev/skills/paruff/ufawkesai/e2e-deployment-validation"><img src="https://agentmods.dev/badge/skills/paruff/ufawkesai/e2e-deployment-validation.svg" alt="Measured on agentmods" 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.00034 | $0.00434 |
| Opus 5 | $0.00017 | $0.00217 |
| Sonnet 5 | $0.00007 | $0.00087 |
| Haiku 4.5 | $0.00003 | $0.00043 |
Grade A, and why
e2e-deployment-validation 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 8d 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 Deployment Validation
Load trigger:
"load e2e-deployment-validation skill"> DORA: Cap 4 (CI/CD Automation) + Cap 6 (Operational Visibility) Token cost: Low
Purpose
Validate that the deployed application behaves correctly after reconciliation.
Responsibilities
- Validate rollout status
- Validate health checks
- Validate logs
- Validate metrics
- Validate trace propagation
Inputs
- Deployed environment
Outputs
deployment-validation.jsonrollout-status.json
Sub-Skills
| Skill | Purpose |
|---|---|
e2e-deployment-validation/rollout |
Validate rollout behavior |
e2e-deployment-validation/telemetry |
Validate logs, metrics, traces |
Validation Rules
- Healthy rollout
- No errors in logs
- Valid metrics
- Valid traces
Output Format
{
"skill": "e2e-deployment-validation",
"status": "pass | fail",
"rollout": { "status": "pass", "replicas": 3, "ready": 3 },
"health": { "liveness": "pass", "readiness": "pass" },
"logs": { "errors": 0, "warnings": 0 },
"metrics": { "present": true, "golden_signals": "complete" },
"traces": { "propagating": true }
}
Success Criteria
- Healthy rollout
- No errors in logs
- Valid metrics and traces
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.
- 8d ago First seen · 70 lines · 34 tokens per session scan A 3e6d932faca8
e2e-deployment-validation is a skill published in the GitHub repository paruff/uFawkesAI (2 stars, last pushed 15d ago), licensed MIT. It adds 34 tokens to every session and 434 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
screen-reader-testing
Test web applications with screen readers including VoiceOver, NVDA, and JAWS. Use when validating screen reader compatibility, debugging accessibility issues, or ensuring assistive technology support.
e2e-testing-patterns
Master end-to-end testing with Playwright and Cypress to build reliable test suites that catch bugs, improve confidence, and enable fast deployment. Use when implementing E2E tests, debugging flaky tests, or establishing testing standards.
qa/e2e-playwright
A method for writing Playwright end-to-end tests, which automate a browser to verify complete user journeys. It covers setup, reusable page objects, login reuse, API mocking, visual checks, multiple browsers and screen sizes, CI, and debugging.
agent-browser
Automates browser interactions for web testing, form filling, screenshots, and data extraction. Use when the user needs to navigate websites, interact with web pages, fill forms, take screenshots, test web applications, or extract information from web pages.
patrol-e2e-testing
Use when writing E2E/integration tests, testing native interactions like permissions or system dialogs, capturing UI regressions, or validating cross-platform behavior (Patrol 4.x).
qa/test-strategy
A testing strategy based on the testing pyramid: many small unit tests, fewer integration tests, and a smaller set of end-to-end tests that follow real user journeys. It also defines checks for security, boundaries, permissions, and business consistency.