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 vignesh2027/AI-AGENT-SKILLS --skill ci-cd-and-automationgit clone --depth 1 https://github.com/vignesh2027/AI-AGENT-SKILLSWrote 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/vignesh2027/ai-agent-skills/ci-cd-and-automation)<a href="https://agentmods.dev/skills/vignesh2027/ai-agent-skills/ci-cd-and-automation"><img src="https://agentmods.dev/badge/skills/vignesh2027/ai-agent-skills/ci-cd-and-automation/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/vignesh2027/ai-agent-skills/ci-cd-and-automation"><img src="https://agentmods.dev/badge/skills/vignesh2027/ai-agent-skills/ci-cd-and-automation.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.00021 | $0.00619 |
| Opus 5 | $0.00010 | $0.00309 |
| Sonnet 5 | $0.00004 | $0.00124 |
| Haiku 4.5 | $0.00002 | $0.00062 |
Grade A, and why
ci-cd-and-automation 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 12d 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 — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Overview
A slow CI pipeline is a productivity killer. A CI pipeline that lets bad code through is worse than no pipeline. This skill designs pipelines that are fast enough to not be skipped, and thorough enough to catch real problems.
When to Use
- When setting up CI/CD for a new project
- When the CI pipeline is slow (>10 minutes)
- When CI is consistently failing for reasons unrelated to code quality
- Before adding a new automated gate to CI
Process
Step 1: Define the pipeline stages
Standard stages:
- Fast checks (<2 min): lint, type check, compile
- Unit tests (<5 min): isolated, no network, no database
- Integration tests (<10 min): with real dependencies
- Security scan: dependency audit, SAST
- Build: Docker image, artifact
- Deploy to staging
- E2E tests against staging
- Deploy to production (gated by manual approval or automated checks)
Step 2: Optimize for speed
- Run stages in parallel where possible
- Cache aggressively: dependencies, build artifacts, Docker layers
- Fail fast: put the fastest checks first
- Target: full pipeline under 15 minutes
Step 3: Required gates before merge
Minimum required to merge a PR:
- All tests pass
- No new high/critical security vulnerabilities (dependency audit)
- Code coverage hasn't regressed (enforced threshold, not aspirational)
- Linting passes (no new lint errors)
Step 4: Required gates before deploy to production
- Staging deploy succeeded
- E2E tests on staging passed
- Performance tests within SLO (for perf-sensitive changes)
- Rollback procedure documented
Step 5: Branch protection
- Main/master branch requires PR (no direct pushes)
- PR requires CI pass + at least 1 review
- Stale approvals invalidated on new commits
Step 6: Environment variable management
- Secrets stored in CI environment variables, not code
- Different secrets per environment (dev/staging/prod never share production secrets)
- Rotate secrets on schedule, not just on breach
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.
- 12d ago First seen · 72 lines · 21 tokens per session scan A c9d138abaef0
ci-cd-and-automation is a skill published in the GitHub repository vignesh2027/AI-AGENT-SKILLS (1 stars, last pushed 14d ago), licensed MIT. It adds 21 tokens to every session and 619 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-08-31.
Other skills, from other repositories
gh-fix-ci
Use when a user asks to debug or fix failing GitHub PR checks that run in GitHub Actions; use gh to inspect checks and logs, summarize failure context, draft a fix plan, and implement only after explicit approval. Treat external providers (for example Buildkite) as out of scope and report only the details URL.
ci-self-heal
A diagnostic guide for analysing failed continuous-integration checks. Continuous integration, or CI, automatically tests and builds code changes; this guide classifies failures and suggests fixes without editing the code.
ci-debugger
A guide for finding the first useful cause of a failed build, test, packaging, deployment, or continuous-integration job. Continuous integration, or CI, automatically checks code in a hosted pipeline.
ci-cd-pipelines
Build automated pipelines that gate merges and ship reliably.
dsh-ci-test-reliability
Design, review, and diagnose DeepSeek Harness tests and fixtures that can fail nondeterministically under CI concurrency, shared host resources, clocks, process-global state, subprocesses, network listeners, or asynchronous teardown. Use when adding or changing tests with those risks, investigating flaky CI, or…
autonomous-loops
Patterns and architectures for autonomous Claude Code loops — from simple sequential pipelines to RFC-driven multi-agent DAG systems.