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 agentmods add skills/kouroshez/coding-os/deployment-cicdnpx skills add kouroshez/coding-os --skill deployment-cicdgit clone --depth 1 https://github.com/kouroshez/coding-osWrote 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/kouroshez/coding-os/deployment-cicd)<a href="https://agentmods.dev/skills/kouroshez/coding-os/deployment-cicd"><img src="https://agentmods.dev/badge/skills/kouroshez/coding-os/deployment-cicd.svg" alt="Measured on agentmods" 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 | $0.00101 | $0.03027 |
| Opus 5 | $0.00051 | $0.01514 |
| Sonnet 5 | $0.00020 | $0.00605 |
| Haiku 4.5 | $0.00010 | $0.00303 |
Grade C, and why
deployment-cicd scanned grade C 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 4d 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
&& rm -rf /var/lib/apt/lists/* Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- **No secrets in image layers.** `RUN curl -H "Bearer $TOKEN"` leaks the token in image history. Use BuildKit secrets or runtime env vars. How it starts
The opening of the file, as written. The whole thing — 261 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Deployment + CI/CD — Ship Safely, Roll Back Fast
A practical playbook for the deploy pipeline that gets a feature from "merged" to "in production" reliably. Stack-agnostic core; recipes assume Docker + GitHub Actions + Kubernetes (the 2026 industry default) with callouts for AWS / GCP / Fly.io specifics.
When to Use This Skill
- Designing CI for a new service — the shape now sets the team's culture.
- Writing or auditing a Dockerfile — bad layers cost minutes per build.
- Choosing between rolling, blue-green, canary, or feature-flag deploys.
- Defining the release process — who clicks deploy, when, and what's reversible.
- Adding semantic versioning + automated changelogs.
- Setting up secrets in CI without leaking them.
- Writing a rollback playbook (preferably before you need it).
- Migrating manual deploys → GitOps (Argo CD / Flux).
Skip when: prototyping a script. Real services, real pipelines.
The Deployment Pipeline — Six Stages
commit → build → test → image → deploy(staging) → deploy(prod)
│ │ │ │ │ │
<1s 1-3m 1-5m 1-2m 1-5m 1-5m + verify
Every stage must be:
- Idempotent — re-running produces the same result.
- Fast-failing — break early, don't ship to staging if unit tests failed.
- Observable — emit deploy markers to metrics so dashboards correlate "the spike" with "the deploy".
- Reversible — every forward step has a documented backward step.
Hard target: commit → prod within 30 minutes for non-DB-migration changes. Slower than that, the team batches and the per-batch risk skyrockets.
Dockerfile — the Five-Layer Rule
A good Dockerfile produces a small, secure, cache-friendly image. Five layers, in this order:
# 1. Base image — minimal, pinned, scanned
FROM python:3.12-slim AS base
# 2. System dependencies — change rarely
RUN apt-get update && apt-get install -y --no-install-recommends \
libpq-dev \
&& rm -rf /var/lib/apt/lists/*
# 3. Language dependencies — change with lock file only
WORKDIR /app
COPY pyproject.toml uv.lock ./
RUN pip install --no-cache-dir uv && uv sync --frozen --no-dev
# 4. Application code — change every commit
COPY src/ src/
# 5. Runtime configuration — labels, user, entrypoint
LABEL org.opencontainers.image.source="https://github.com/org/repo"
RUN useradd --uid 1000 --no-create-home app
USER 1000
EXPOSE 8000
CMD ["uv", "run", "uvicorn", "src.main:app", "--host", "0.0.0.0", "--port", "8000"]
What ships with it
3 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.
- 4d ago First seen · 261 lines · 101 tokens per session scan C 6d47da2e9682
deployment-cicd is a skill published in the GitHub repository kouroshez/coding-os (6 stars, last pushed 4d ago), licensed Apache-2.0. It adds 101 tokens to every session and 3,027 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it C with 2 findings (recursive force delete, 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
deployment-patterns
Deployment workflows, CI/CD pipeline patterns, Docker containerization, health checks, rollback strategies, and production readiness checklists for web applications. Use when setting up deployment infrastructure or planning releases.
scanning-containers-with-trivy-in-cicd
This skill covers integrating Aqua Security's Trivy scanner into CI/CD pipelines for comprehensive container image vulnerability detection. It addresses scanning Docker images for OS package and application dependency CVEs, detecting misconfigurations in Dockerfiles, scanning filesystem and git repositories, and…
konflux-build
Create a manual Konflux build from a PR with configurable image expiry (default 30 days).
performing-container-security-scanning-with-trivy
Scan container images, filesystems, and Kubernetes manifests for vulnerabilities, misconfigurations, exposed secrets, and license compliance issues using Aqua Security Trivy with SBOM generation and CI/CD integration.
devops
DevOps - Docker, CI/CD, cloud infra, monitoring.
devops-deployment
Use when setting up CI/CD pipelines, containerizing applications, deploying to Kubernetes, or writing infrastructure as code. DevOps & Deployment covers GitHub Actions, Docker, Helm, and Terraform patterns.