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 ApexIQ/skillsmith --skill ci_cd_best_practicesgit clone --depth 1 https://github.com/ApexIQ/skillsmithWrote 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/apexiq/skillsmith/ci_cd_best_practices)<a href="https://agentmods.dev/skills/apexiq/skillsmith/ci_cd_best_practices"><img src="https://agentmods.dev/badge/skills/apexiq/skillsmith/ci_cd_best_practices/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/apexiq/skillsmith/ci_cd_best_practices"><img src="https://agentmods.dev/badge/skills/apexiq/skillsmith/ci_cd_best_practices.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.00030 | $0.00581 |
| Opus 5 | $0.00015 | $0.00291 |
| Sonnet 5 | $0.00006 | $0.00116 |
| Haiku 4.5 | $0.00003 | $0.00058 |
Grade A, and why
ci-cd-best-practices 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 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.
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 Best Practices
Goal: Ship fast, ship safe, ship often.
1. Pipeline Strategy
For Monorepos
- Change Detection: Only run jobs for changed packages.
- Tools: Nx, Turborepo, or path filters in GitHub Actions/GitLab CI.
For Standard Repos
- Run full pipeline on every push to feature branches.
- Optimize with caching and parallelization.
2. CI: The Feedback Loop
- Speed Target: Pipeline should finish in <10 minutes.
- Parallelization: Run lint, test, and build concurrently.
- Caching:
- Cache dependencies (
node_modules, Python venv). - Cache build artifacts and Docker layers.
- Cache dependencies (
3. Quality Gates
| Gate | Tools | Action on Failure |
|---|---|---|
| Linting | ESLint, Ruff, Pylint | Block merge |
| Unit Tests | Jest, Pytest | Block merge |
| Security | npm audit, Bandit, Snyk | Block merge (high/critical) |
| Coverage | Istanbul, Coverage.py | Warn if below threshold |
4. CD: Deployment
- Immutable Artifacts: Build once, deploy everywhere.
- Build Docker image -> Tag with commit SHA -> Push to registry.
- Zero Downtime: Use rolling updates or blue-green deployments.
- Environment Parity: Staging should mirror Production.
5. Example Workflow (GitHub Actions)
version: 0.1.0
name: CI
on: [push, pull_request]
jobs:
lint:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
- run: npm ci --cache .npm
- run: npm run lint
test:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
- run: npm ci --cache .npm
- run: npm test
build:
needs: [lint, test]
runs-on: ubuntu-latest
steps:
- run: npm run build
Guidelines
- Keep pipelines simple and readable.
- Fail fast: run fastest checks first.
- Use secrets management for API keys (never hardcode).
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 · 85 lines · 30 tokens per session scan A e42bd9686e3c
ci-cd-best-practices is a skill published in the GitHub repository ApexIQ/skillsmith (5 stars, last pushed 5mo ago), licensed MIT. It adds 30 tokens to every session and 581 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-08-31.
Other skills, from other repositories
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.
GitHub Actions CI Patterns
Use this skill when adding or debugging GitHub Actions workflows and you want repeatable CI behavior, minimal permissions, and clear failure logs.
ci-cd-pipeline
Create and optimize CI/CD pipelines with GitHub Actions, automated testing, deployment, and release workflows. Use when setting up continuous integration, deployment automation, or improving build pipelines.
DevOps & Deployment
CI/CD pipelines, containerization, Kubernetes, and infrastructure as code patterns.
github-release-management
Comprehensive GitHub release orchestration with AI swarm coordination for automated versioning, testing, deployment, and rollback management.