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 sawrus/agent-guides --skill ci-cd-pipelinesgit clone --depth 1 https://github.com/sawrus/agent-guidesWrote 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/sawrus/agent-guides/ci-cd-pipelines)<a href="https://agentmods.dev/skills/sawrus/agent-guides/ci-cd-pipelines"><img src="https://agentmods.dev/badge/skills/sawrus/agent-guides/ci-cd-pipelines/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/sawrus/agent-guides/ci-cd-pipelines"><img src="https://agentmods.dev/badge/skills/sawrus/agent-guides/ci-cd-pipelines.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00044 | $0.00437 |
| Opus 5.5 | $0.00018 | $0.00175 |
| Sonnet 5.5 | $0.00009 | $0.00087 |
| Haiku 4.5 | $0.00004 | $0.00044 |
Grade A, and why
ci-cd-pipelines 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 5d 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: CI/CD Pipeline Patterns
When to load
When designing GitHub Actions workflows, optimizing pipeline speed, implementing deployment gates.
Pipeline Structure
.github/workflows/
├── ci.yml # Every PR: lint, test, build, security scan
├── deploy-stg.yml # Merge to main: deploy to staging
└── deploy-prd.yml # Release tag: deploy to production (with approval)
CI Template
jobs:
validate:
steps:
- uses: actions/cache@v4
with:
path: ~/.npm
key: ${{ runner.os }}-node-${{ hashFiles('**/package-lock.json') }}
- run: npm ci
- run: npm run lint && npm run typecheck && npm test -- --coverage
terraform-validate:
steps:
- uses: hashicorp/setup-terraform@v3
- run: terraform init -backend=false && terraform validate && terraform fmt -check -recursive
working-directory: terraform/
security:
steps:
- uses: aquasecurity/trivy-action@master
with: { scan-type: fs, severity: HIGH,CRITICAL, exit-code: 1 }
Deployment Gate
jobs:
deploy:
environment: production # Requires reviewer approval in GitHub Environments
steps:
- run: kubectl set image deployment/api api=$IMAGE
- run: npm run test:smoke -- --env production
Pipeline Optimization Checklist
- Dependencies cached with hash-based keys
- Independent jobs parallelized (lint + test + security)
- Docker layer caching enabled
- Matrix builds for multi-version testing
- Concurrency groups prevent redundant runs on same branch
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.
- 5d ago Changed · +5 lines · +44 tokens per session 19315a574b12
- 1mo ago First seen · 59 lines · 0 tokens per session scan A e189d4456641
ci-cd-pipelines is a skill published in the GitHub repository sawrus/agent-guides (19 stars, last pushed yesterday), licensed MIT. It adds 44 tokens to every session and 437 once invoked, about $0.0002 per session on Opus 5.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
git-workflow-and-versioning
Structures git workflow practices. Use when making any code change. Use when committing, branching, resolving conflicts, splitting uncommitted work in a messy working tree into clean atomic commits, opening or reviewing a pull request (PR), pushing to a remote, or when you need to organize work across multiple…
antigravity-maintainer-batch-release
Run protected AAS maintainer sweeps, PR merge batches, resumable review, immutable distribution, Core checks, and scripted releases. Use for repository maintenance, main alignment, CLI/MCP/Workbench changes, or release work; not ordinary contribution tasks.
app-store-changelog
Generate user-facing App Store release notes from git history since the last tag.
releasing-prod
A controlled process for deploying already tested changes to the production environment. Production is the live environment used by users, and this process includes owner approval, database migration checks, deployment, and smoke tests.
npm-trusted-publishing
Use when setting up npm publishing with GitHub Actions - provides trusted publishing with OIDC, provenance attestations, and monorepo configuration.
production-deployment
Zero-downtime deployments with pre-flight checks, staged rollouts, and rollback plans. Never ship to production without a verified rollback strategy.