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 san-npm/skills-ws --skill ci-cd-pipelinegit clone --depth 1 https://github.com/san-npm/skills-wsWrote 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/san-npm/skills-ws/ci-cd-pipeline)<a href="https://agentmods.dev/skills/san-npm/skills-ws/ci-cd-pipeline"><img src="https://agentmods.dev/badge/skills/san-npm/skills-ws/ci-cd-pipeline/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/san-npm/skills-ws/ci-cd-pipeline"><img src="https://agentmods.dev/badge/skills/san-npm/skills-ws/ci-cd-pipeline.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.00082 | $0.00528 |
| Opus 5 | $0.00041 | $0.00264 |
| Sonnet 5 | $0.00016 | $0.00106 |
| Haiku 4.5 | $0.00008 | $0.00053 |
Grade A, and why
ci-cd-pipeline 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
CI/CD Pipeline Engineering
Safety gate
Before executing commands or changing external systems, confirm scope, credentials, target environment, rollback, and required approval. Pin and verify third-party artifacts; never expose secrets to client code or logs.
Reference guide
Read only the references needed for the current request:
- Philosophy: references/philosophy.md
- GitHub Actions: Complete Production Workflow: references/github-actions-complete-production-workflow.md
- Testing Pyramid: What to Run Where: references/testing-pyramid-what-to-run-where.md
- Deployment Pipeline: Complete Production Workflow: references/deployment-pipeline-complete-production-workflow.md
- Supply-Chain Security: SLSA Provenance + Keyless Signing: references/supply-chain-security-slsa-provenance-keyless-signing.md
- Rollback Strategies: references/rollback-strategies.md
- Feature Flags: references/feature-flags.md
- Release Management: references/release-management.md
- Monorepo CI: Only Build What Changed: references/monorepo-ci-only-build-what-changed.md
- Secrets Management in CI: references/secrets-management-in-ci.md
- Performance Tips: references/performance-tips.md
- Anti-Patterns: references/anti-patterns.md
- Checklist: Production-Ready Pipeline: references/checklist-production-ready-pipeline.md
What ships with it
14 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.
- agents/openai.yaml 199 B
- references/anti-patterns.md 872 B
- references/checklist-production-ready-pipeline.md 1.4 KB
- references/deployment-pipeline-complete-production-workflow.md 8.3 KB
- references/feature-flags.md 1.6 KB
- references/github-actions-complete-production-workflow.md 8.8 KB
- references/monorepo-ci-only-build-what-changed.md 833 B
- references/performance-tips.md 710 B
- references/philosophy.md 506 B
- references/release-management.md 1.7 KB
- references/rollback-strategies.md 2.0 KB
- references/secrets-management-in-ci.md 1.3 KB
- references/supply-chain-security-slsa-provenance-keyless-signing.md 4.1 KB
- references/testing-pyramid-what-to-run-where.md 2.9 KB
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 First seen · 28 lines · 82 tokens per session scan A 0d2d558e9a5b
ci-cd-pipeline is a skill published in the GitHub repository san-npm/skills-ws (2 stars, last pushed 5d ago), licensed MIT. It adds 82 tokens to every session and 528 once invoked, about $0.0004 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-07.
Other skills, from other repositories
Verification & Quality Assurance
Comprehensive truth scoring, code quality verification, and automatic rollback system with 0.95 accuracy threshold for ensuring high-quality agent outputs and codebase reliability.
ci
Configure Ginkgo for continuous integration — the recommended CLI flag set and the rationale for each flag (-r -p --randomize-all --randomize-suites --fail-on-pending --fail-on-empty --keep-going --cover --race --trace --json-report --timeout --poll-progress-after/-interval), invoking via go run to pin the CLI to…
migrate-vstest-to-mtp
Use this skill before answering, planning, or editing whenever .NET tests or CI are switching from VSTest to Microsoft.Testing.Platform (MTP), or an MTP migration behaves differently. Triggers include "switch from VSTest"; MSTest/NUnit/xUnit MTP enablement; OutputType=Exe only for test projects in…
playwright-ci
Production-ready CI/CD configurations for Playwright — GitHub Actions, GitLab CI, CircleCI, Azure DevOps, Jenkins, Docker, parallel sharding, reporting, code coverage, and global setup/teardown.
ci-maintenance-workflow
CI and GitHub Actions maintenance workflows — fix a failing test from a CI URL, fix a failing smoke test, add @pytest.mark.slow markers to slow tests, or review a PR against agent-checkable standards. Use when user asks to fix a failing test, fix a smoke test, mark slow tests, or review a PR. Trigger when the user…
playwright-testing
E2E testing with Playwright - Page Objects, cross-browser, CI/CD.