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 pipeline-test-stage-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/pipeline-test-stage-validation)<a href="https://agentmods.dev/skills/paruff/ufawkesai/pipeline-test-stage-validation"><img src="https://agentmods.dev/badge/skills/paruff/ufawkesai/pipeline-test-stage-validation/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/pipeline-test-stage-validation"><img src="https://agentmods.dev/badge/skills/paruff/ufawkesai/pipeline-test-stage-validation.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.00033 | $0.00761 |
| Opus 5 | $0.00016 | $0.00380 |
| Sonnet 5 | $0.00007 | $0.00152 |
| Haiku 4.5 | $0.00003 | $0.00076 |
Grade A, and why
pipeline-test-stage-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 7d 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 — 131 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: Pipeline Test Stage Validation
Load trigger:
"load pipeline-test-stage-validation skill"> DORA: Cap 1 (AI Policy) Token cost: Low
Purpose
Ensure the CI/CD pipeline includes required test stages.
Responsibilities
- Validate presence of unit test stage
- Validate presence of integration test stage
- Validate presence of E2E test stage (if required)
- Validate coverage reporting stage
- Validate test result reporting
Inputs
pipeline-spec.yaml- Governance rules
Outputs
pipeline-test-stage-report.json
Required Stages
Must Have
| Stage | Purpose | Required |
|---|---|---|
| Unit tests | Fast correctness check | Yes |
| Coverage report | Measure coverage | Yes |
| Lint/format | Code quality | Yes |
Should Have
| Stage | Purpose | Required |
|---|---|---|
| Integration tests | Component interaction | Recommended |
| Security scan | Vulnerability check | Recommended |
Nice to Have
| Stage | Purpose | Required |
|---|---|---|
| E2E tests | Full workflow validation | If applicable |
| Performance smoke | Basic perf check | Optional |
Validation Rules
Stage Presence
- Unit test stage exists
- Coverage reporting stage exists
- Integration test stage exists (or justified as N/A)
- E2E test stage exists (if app has UI or API workflows)
Stage Configuration
- Test stages run on PR and push to main
- Test failures block merge
- Coverage thresholds enforced in CI
- Test results reported (not just exit code)
Pipeline Position
- Tests run before build/deploy stages
- Tests run after lint/format stages
- Security scans run alongside tests
Tools
yqfor YAML parsing- Policy engine (OPA, Kyverno) for validation
gh apifor GitHub Actions workflow inspection
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.
- 7d ago First seen · 131 lines · 33 tokens per session scan A bcf061d7aa96
pipeline-test-stage-validation is a skill published in the GitHub repository paruff/uFawkesAI (2 stars, last pushed 18d ago), licensed MIT. It adds 33 tokens to every session and 761 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-09-03.
Other skills, from other repositories
CI Pipeline Optimizer
Optimize CI test pipelines through intelligent test splitting, parallelization, caching strategies, and selective test execution based on code changes.
Flaky Test Quarantine
Detect, quarantine, and systematically fix flaky tests with automated retry analysis, root cause categorization, and CI pipeline integration for test reliability.
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.
Advanced Chaos Engineering
Advanced chaos engineering patterns using Chaos Monkey, Litmus, and Gremlin for testing distributed system resilience under failure conditions.
CI/CD Pipeline Config
CI/CD pipeline configuration skill for test automation, covering GitHub Actions, Jenkins, GitLab CI, test parallelization, reporting, and artifact management.