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 vanja-emichi/a0_agent_skills --skill ci-cd-and-automationgit clone --depth 1 https://github.com/vanja-emichi/a0_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/vanja-emichi/a0_agent_skills/ci-cd-and-automation)<a href="https://agentmods.dev/skills/vanja-emichi/a0_agent_skills/ci-cd-and-automation"><img src="https://agentmods.dev/badge/skills/vanja-emichi/a0_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/vanja-emichi/a0_agent_skills/ci-cd-and-automation"><img src="https://agentmods.dev/badge/skills/vanja-emichi/a0_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.00041 | $0.02692 |
| Opus 5 | $0.00020 | $0.01346 |
| Sonnet 5 | $0.00008 | $0.00538 |
| Haiku 4.5 | $0.00004 | $0.00269 |
Grade B, and why
ci-cd-and-automation scanned grade B with 2 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 11d 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
# Don't run as root Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
CMD wget -qO- http://localhost:3000/health || exit 1 How it starts
The opening of the file, as written. The whole thing — 408 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CI/CD and Automation
Overview
Automate the path from code to production. CI/CD pipelines give every change a consistent, repeatable journey through testing, validation, and deployment. The goal is a pipeline where passing tests is sufficient confidence to deploy — not a process that needs to be worked around.
When to Use
- Setting up a new project's CI/CD pipeline
- Adding automated testing to an existing pipeline
- Configuring deployment automation
- Setting up infrastructure as code
- Adding security scanning or quality gates
- Implementing preview environments for PRs
Pipeline Architecture
The Four Stages
┌─────────┐ ┌─────────┐ ┌──────────┐ ┌─────────────┐
│ CI │ │ Test │ │ Security │ │ Deploy │
│ │───▶│ │───▶│ │───▶│ │
│ Build │ │ Unit │ │ Audit │ │ Staging │
│ Lint │ │ Integr. │ │ SAST │ │ Production │
│ Types │ │ E2E │ │ Secrets │ │ (gated) │
└─────────┘ └─────────┘ └──────────┘ └─────────────┘
↑ ↑ ↑ ↑
Every push Every push Every push Main only
Stage Principles
- Fast feedback first: Lint and type-check before running slow tests
- Fail fast: Stop the pipeline at the first failure
- Parallel where safe: Run independent jobs concurrently
- Deterministic: Same commit always produces same result
- Cached: Restore dependencies from cache before installing
GitHub Actions Examples
Basic CI Pipeline
# .github/workflows/ci.yml
name: CI
on:
push:
branches: [main]
pull_request:
branches: [main]
jobs:
quality:
name: Quality Checks
runs-on: ubuntu-latest
steps:
- name: Checkout
uses: actions/checkout@v4
- name: Setup Node.js
uses: actions/setup-node@v4
with:
node-version: '20'
cache: 'npm'
- name: Install dependencies
run: npm ci
- name: Type check
run: npm run type-check
- name: Lint
run: npm run lint
- name: Unit tests
run: npm run test:unit -- --coverage
- name: Upload coverage
uses: codecov/codecov-action@v4
with:
token: ${{ secrets.CODECOV_TOKEN }}
build:
name: Build
runs-on: ubuntu-latest
needs: quality
steps:
- uses: actions/checkout@v4
- uses: actions/setup-node@v4
with:
node-version: '20'
cache: 'npm'
- run: npm ci
- run: npm run build
- name: Upload build artifact
uses: actions/upload-artifact@v4
with:
name: build
path: dist/
retention-days: 7
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.
- 11d ago First seen · 408 lines · 41 tokens per session scan B a95fbed9234c
ci-cd-and-automation is a skill published in the GitHub repository vanja-emichi/a0_agent_skills (5 stars, last pushed 1mo ago), licensed MIT. It adds 41 tokens to every session and 2,692 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it B with 2 findings (asks for root, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
github-release-management
Comprehensive GitHub release orchestration with AI swarm coordination for automated versioning, testing, deployment, and rollback management.
github-release-management
Comprehensive GitHub release orchestration with AI swarm coordination for automated versioning, testing, deployment, and rollback management.
cicd-expert
Expert-level CI/CD with GitHub Actions, Jenkins, deployment pipelines, and automation. Use when the user mentions CI/CD, GitHub Actions, Jenkins, GitLab CI, deployment, or automation, or when the task involves CI/CD Fundamentals, Pipeline Design, Workflow Basics, or Docker Build and Push.
ci-cd-pipeline
Design and implement CI/CD pipelines for automated testing and deployment.
cicd-agent
CI/CD pipeline design and review — GitHub Actions, pipeline best practices, secrets management, deployment strategies, and release automation.
github-release-management
Comprehensive GitHub release orchestration with AI swarm coordination for automated versioning, testing, deployment, and rollback management.