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 The-AI-Directory-Company/agents-and-skills --skill ci-cd-pipeline-designgit clone --depth 1 https://github.com/The-AI-Directory-Company/agents-and-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/the-ai-directory-company/agents-and-skills/ci-cd-pipeline-design)<a href="https://agentmods.dev/skills/the-ai-directory-company/agents-and-skills/ci-cd-pipeline-design"><img src="https://agentmods.dev/badge/skills/the-ai-directory-company/agents-and-skills/ci-cd-pipeline-design/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/the-ai-directory-company/agents-and-skills/ci-cd-pipeline-design"><img src="https://agentmods.dev/badge/skills/the-ai-directory-company/agents-and-skills/ci-cd-pipeline-design.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.00047 | $0.01635 |
| Opus 5 | $0.00023 | $0.00817 |
| Sonnet 5 | $0.00009 | $0.00327 |
| Haiku 4.5 | $0.00005 | $0.00163 |
Grade A, and why
ci-cd-pipeline-design 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 8d 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 — 160 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CI/CD Pipeline Design
Before you start
Gather the following from the user:
- Which CI/CD platform? (GitHub Actions, GitLab CI, CircleCI, or platform-agnostic)
- What language/runtime? (Node.js, Python, Go, Java, Rust, multi-language)
- What needs to happen? (Lint, test, build, deploy — which of these?)
- Where does it deploy? (Vercel, AWS, GCP, Kubernetes, static hosting)
- What is the branching strategy? (Trunk-based, GitFlow, feature branches)
- What is slow today? (If optimizing an existing pipeline, what takes the longest?)
If the user says "set up CI/CD," push back: "For which platform, language, and deployment target? I also need your branching strategy to design the trigger rules."
Procedure
Step 1: Define trigger rules
Map git events to pipeline runs:
# GitHub Actions example
on:
pull_request:
branches: [main] # Run tests on PRs to main
push:
branches: [main] # Deploy on merge to main
tags: ["v*"] # Deploy releases on version tags
workflow_dispatch: # Manual trigger for ad-hoc runs
Rules:
- PRs trigger lint + test + build (no deploy)
- Merge to main triggers lint + test + build + deploy to staging
- Tags trigger deploy to production
- Never auto-deploy to production on push to main
Step 2: Design the stage graph
Organize jobs into stages with dependency edges:
[Lint] ──┐
├──> [Build] ──> [Deploy Staging] ──> [Smoke Test] ──> [Deploy Prod]
[Test] ──┘
For each stage, document:
| Stage | Trigger | Depends on | Timeout | Runs on |
|---|---|---|---|---|
| Lint | PR + push | None | 5 min | ubuntu-latest |
| Test | PR + push | None | 15 min | ubuntu-latest |
| Build | PR + push | Lint + Test pass | 10 min | ubuntu-latest |
| Deploy staging | Push to main | Build | 10 min | ubuntu-latest |
| Smoke test | After staging deploy | Deploy staging | 5 min | ubuntu-latest |
| Deploy prod | Tag v* or manual | Smoke test pass | 10 min | ubuntu-latest |
What ships with it
4 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.
- 8d ago First seen · 160 lines · 47 tokens per session scan A 8ef00b2fe3f5
ci-cd-pipeline-design is a skill published in the GitHub repository The-AI-Directory-Company/agents-and-skills (2 stars, last pushed 5mo ago), licensed MIT. It adds 47 tokens to every session and 1,635 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
devops-cloud
DevOps, cloud infrastructure, and platform engineering. Use when working with AWS, GCP, Azure, Kubernetes, Terraform, CI/CD pipelines, or infrastructure as code.
integrating-sast-into-github-actions-pipeline
This skill covers integrating Static Application Security Testing (SAST) tools—CodeQL and Semgrep—into GitHub Actions CI/CD pipelines. It addresses configuring automated code scanning on pull requests and pushes, tuning rules to reduce false positives, uploading SARIF results to GitHub Advanced Security, and…
integrating-dast-with-owasp-zap-in-pipeline
This skill covers integrating OWASP ZAP (Zed Attack Proxy) for Dynamic Application Security Testing in CI/CD pipelines. It addresses configuring baseline, full, and API scans against running applications, interpreting ZAP findings, tuning scan policies, and establishing DAST quality gates in GitHub Actions and GitLab…
performing-sca-dependency-scanning-with-snyk
This skill covers implementing Software Composition Analysis (SCA) using Snyk to detect vulnerable open-source dependencies in CI/CD pipelines. It addresses scanning package manifests and lockfiles, automated fix pull request generation, license compliance checking, continuous monitoring of deployed applications, and…
securing-github-actions-workflows
This skill covers hardening GitHub Actions workflows against supply chain attacks, credential theft, and privilege escalation. It addresses pinning actions to SHA digests, minimizing GITHUBTOKEN permissions, protecting secrets from exfiltration, preventing script injection in workflow expressions, and implementing…
implementing-aqua-security-for-container-scanning
Deploy Aqua Security's Trivy scanner to detect vulnerabilities, misconfigurations, secrets, and license issues in container images across CI/CD pipelines and registries.