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 d-o-hub/github-template-ai-agents --skill cicd-pipelinegit clone --depth 1 https://github.com/d-o-hub/github-template-ai-agentsWrote 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/d-o-hub/github-template-ai-agents/cicd-pipeline)<a href="https://agentmods.dev/skills/d-o-hub/github-template-ai-agents/cicd-pipeline"><img src="https://agentmods.dev/badge/skills/d-o-hub/github-template-ai-agents/cicd-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/d-o-hub/github-template-ai-agents/cicd-pipeline"><img src="https://agentmods.dev/badge/skills/d-o-hub/github-template-ai-agents/cicd-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.00099 | $0.01421 |
| Opus 5 | $0.00049 | $0.00711 |
| Sonnet 5 | $0.00020 | $0.00284 |
| Haiku 4.5 | $0.00010 | $0.00142 |
Grade A, and why
cicd-pipeline scanned grade A with 1 finding 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 9d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
bash <(curl -Ls https://coverage.codacy.com/get.sh) report -r <coverage-report-file> How it starts
The opening of the file, as written. The whole thing — 156 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CI/CD Pipeline
Design and implement efficient, secure, and reliable CI/CD pipelines.
When to Use
- User asks to set up, optimize, or troubleshoot CI/CD pipelines
- Configuring workflow triggers or managing secrets in pipelines
- Handling pipeline failures or implementing deployment strategies
- Even if they just say "set up CI" or "fix the pipeline"
Platform Comparison
| Platform | Config Location | Runner | Secrets |
|---|---|---|---|
| GitHub Actions | .github/workflows/ |
GitHub-hosted or self-hosted | secrets.* context |
| GitLab CI | .gitlab-ci.yml |
Shared or specific runners | $CI_JOB_VAULT |
| Forgejo Actions | .forgejo/workflows/ |
Docker or host | Repository secrets |
Pipeline Design Workflow
- Define triggers — Push, PR, schedule, or manual dispatch. Use
pathsfilters to skip unnecessary runs. - Structure jobs — Separate lint, test, build, and deploy into distinct jobs. Use dependencies for ordering.
- Add caching — Cache dependencies (npm, pip, cargo) between runs. Reduces build times 30-70%.
- Manage secrets — Never hardcode tokens. Use platform secret stores and rotate regularly.
- Add security scanning — Run SAST, dependency scanning, and secret detection in CI.
- Configure notifications — Alert on failures to Slack, Discord, or email.
Common Failure Patterns
| Symptom | Likely Cause | Fix |
|---|---|---|
| Timeout on checkout | Shallow clone + large repo | Increase fetch-depth or use --depth 1 |
| OOM during test | Too many parallel tests | Limit concurrency or add swap |
| Flaky test failures | Race conditions or external deps | Quarantine flaky tests, add retries |
| Secret not found | Wrong environment scope | Verify secret is available in the correct job/environment |
| Cache not restoring | Cache key mismatch | Use hashFiles() for deterministic keys |
Gotchas
- GitHub Actions
GITHUB_TOKENexpires after 1 hour — don't use it for long-running workflows. - GitLab CI
rules:andonly/exceptare mutually exclusive — pick one per job. - Forgejo Actions are compatible with GitHub Actions syntax but may lag behind on new features.
- Matrix builds multiply cost — a 3x3 matrix runs 9 jobs, not 3.
- Artifact retention defaults vary by platform — set explicit retention to avoid storage costs.
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.
- 9d ago First seen · 156 lines · 99 tokens per session scan A ad26ca101cf4
cicd-pipeline is a skill published in the GitHub repository d-o-hub/github-template-ai-agents (2 stars, last pushed yesterday), licensed MIT. It adds 99 tokens to every session and 1,421 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it A with 1 finding (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
ci-cd-and-automation
Design pipelines with Shift Left checks, quality gates, feature flags, and fast failure feedback.
devops-cloud
DevOps, cloud infrastructure, and platform engineering. Use when working with AWS, GCP, Azure, Kubernetes, Terraform, CI/CD pipelines, or infrastructure as code.
cc-devops-skills
SRE, DevOps, Kubernetes, CI/CD, PromQL, Terraform, Docker, and incident operations playbook for building reliable delivery and operations workflows.
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…
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.
implementing-code-signing-for-artifacts
This skill covers implementing code signing for build artifacts to ensure integrity and authenticity throughout the software supply chain. It addresses signing binaries, packages, and containers using GPG, Sigstore, and platform-specific signing tools, establishing trust chains, and verifying signatures in deployment…