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-policygit 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-policy)<a href="https://agentmods.dev/skills/paruff/ufawkesai/pipeline-policy"><img src="https://agentmods.dev/badge/skills/paruff/ufawkesai/pipeline-policy/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-policy"><img src="https://agentmods.dev/badge/skills/paruff/ufawkesai/pipeline-policy.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.00027 | $0.00598 |
| Opus 5 | $0.00014 | $0.00299 |
| Sonnet 5 | $0.00005 | $0.00120 |
| Haiku 4.5 | $0.00003 | $0.00060 |
Grade A, and why
pipeline-policy 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.
How it starts
The opening of the file, as written. The whole thing — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: Pipeline Policy Validation
Load trigger:
"load pipeline-policy skill"> DORA: Cap 1 (AI Policy) Token cost: Low
Purpose
Validate CI/CD pipeline correctness.
Responsibilities
- Validate required stages present
- Validate security gates included
- Validate SBOM and signing stages
- Validate test coverage thresholds enforced
Inputs
pipeline-spec.yaml- Governance rules
Outputs
pipeline-policy.json
Validation Rules
Required Stages
- Lint/format stage present
- Unit test stage present
- Integration test stage present (or justified N/A)
- Security scan stage present
- Build stage present
- Deploy stage present (with approval gate)
Security Gates
- SAST scan stage present
- SCA/dependency scan stage present
- Image signing stage present (if containers)
- SBOM generation stage present (if release artifacts)
Gating
- Test failures block merge
- Security scan failures block merge
- Deployment requires manual approval
- Coverage thresholds enforced
Hardening
- Actions pinned to commit SHAs
- Secrets accessed via
${{ secrets.NAME }} - No secrets logged
- Least privilege permissions
Tools
yqfor YAML parsing- Policy engine (OPA, Kyverno) for validation
gh apifor GitHub Actions inspection
Output Format
{
"skill": "pipeline-policy",
"status": "pass | fail",
"stages": {
"lint": { "present": true, "required": true },
"unit_test": { "present": true, "required": true },
"integration_test": { "present": true, "required": true },
"security_scan": { "present": true, "required": true },
"build": { "present": true, "required": true },
"deploy": { "present": true, "required": true, "approval_required": true }
},
"gates": {
"sast": true,
"sca": true,
"signing": true,
"sbom": true
},
"violations": []
}
Success Criteria
- Pipeline complies with governance rules
- All required stages present
- Security gates enforced
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 · 103 lines · 27 tokens per session scan A 28eb0e9b299e
pipeline-policy is a skill published in the GitHub repository paruff/uFawkesAI (2 stars, last pushed 20d ago), licensed MIT. It adds 27 tokens to every session and 598 once invoked, about $0.0001 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
template-shell
Shell helper scripts for the template research framework. Covers system health checks, local CI reproduction, uv bootstrap, and rsync backup/restore contracts under scripts/shell/.
ci-cd-and-automation
Automates CI/CD pipeline setup. Use when setting up or modifying build and deployment pipelines. Use when you need to automate quality gates, configure test runners in CI, or establish deployment strategies.
deployment-pipeline-design
Design multi-stage CI/CD pipelines with approval gates, security checks, and deployment orchestration. Use this skill when designing zero-downtime deployment pipelines, implementing canary rollout strategies, setting up multi-environment promotion workflows, or debugging failed deployment gates in CI/CD.
gitlab-ci-patterns
Build GitLab CI/CD pipelines with multi-stage workflows, caching, and distributed runners for scalable automation. Use when implementing GitLab CI/CD, optimizing pipeline performance, or setting up automated testing and deployment.
bazel-build-optimization
Optimize Bazel builds for large-scale monorepos. Use when configuring Bazel, implementing remote execution, or optimizing build performance for enterprise codebases.
planning-with-files
Persistent file-based planning for multi-step AI-agent work. Keeps taskplan.md, findings.md, and progress.md on disk; lifecycle hooks inject selected project planning context. Automatic recovery reads project planning files only. Explicit session-catchup.py --metadata reads same-project local agent session records and…