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 pipe-to-obsgit 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/pipe-to-obs)<a href="https://agentmods.dev/skills/paruff/ufawkesai/pipe-to-obs"><img src="https://agentmods.dev/badge/skills/paruff/ufawkesai/pipe-to-obs/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/pipe-to-obs"><img src="https://agentmods.dev/badge/skills/paruff/ufawkesai/pipe-to-obs.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.00491 |
| Opus 5 | $0.00020 | $0.00246 |
| Sonnet 5 | $0.00008 | $0.00098 |
| Haiku 4.5 | $0.00004 | $0.00049 |
Grade A, and why
pipe-to-obs-integration 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.
What it actually says
Skill: PIPE → OBS Integration Testing
Load trigger:
"load pipe-to-obs-integration skill"> DORA: Cap 4 (CI/CD Automation) Token cost: Low
Purpose
Validate artifact flow and GitOps updates triggered by PIPE.
Responsibilities
- Execute a full PIPE build
- Validate that OBS receives correct artifacts
- Validate that OBS updates GitOps manifests correctly
- Validate version.json, SBOM, signatures, and image digests
Inputs
- Pipeline run
version.json- GitOps repo
Outputs
pipe-obs-report.jsonmanifest-diff.txt
Sub-Skills
| Skill | Purpose |
|---|---|
pipe-to-obs/artifact-flow |
Validate artifact production and consumption |
pipe-to-obs/manifest-update |
Validate manifest updates |
Integration Flow
PIPE build → artifacts → OBS receives → OBS updates GitOps → manifests validated
Validation Rules
- Correct image tag passed to OBS
- Correct image digest passed to OBS
- OBS creates valid Git commit
- Manifests valid YAML
- No schema violations
Output Format
{
"skill": "pipe-to-obs-integration",
"status": "pass | fail",
"pipeline_run": "123",
"artifacts": {
"version_json": "present",
"sbom": "present",
"signature": "present",
"image_digest": "present"
},
"obs_update": {
"commit": "abc123",
"files_changed": 3,
"manifests_valid": true
}
}
Success Criteria
- Correct image tag and digest passed to OBS
- Correct GitOps update created
- No invalid manifests
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.
- 7d ago First seen · 85 lines · 41 tokens per session scan A ccda41ef9e8f
pipe-to-obs-integration is a skill published in the GitHub repository paruff/uFawkesAI (2 stars, last pushed 18d ago), licensed MIT. It adds 41 tokens to every session and 491 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
github-actions-templates
Create production-ready GitHub Actions workflows for automated testing, building, and deploying applications. Use when setting up CI/CD with GitHub Actions, automating development workflows, or creating reusable workflow templates.
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.
devops-infrastructure
Guides Docker, CI/CD pipelines, deployment strategies, infrastructure as code, and observability setup. Use when writing Dockerfiles, configuring GitHub Actions, planning deployments, setting up monitoring, or when asked about containers, pipelines, Terraform, or production infrastructure.
CI/CD Pipeline Advanced
Expert-level CI/CD pipeline skill for test automation. Covers GitHub Actions, Jenkins, GitLab CI, Azure DevOps, parallel execution, matrix strategies, caching, artifact management, and deployment gates.
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.