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 ashermahonin/agentic-skills --skill cicd-automationgit clone --depth 1 https://github.com/ashermahonin/agentic-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/ashermahonin/agentic-skills/cicd-automation)<a href="https://agentmods.dev/skills/ashermahonin/agentic-skills/cicd-automation"><img src="https://agentmods.dev/badge/skills/ashermahonin/agentic-skills/cicd-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/ashermahonin/agentic-skills/cicd-automation"><img src="https://agentmods.dev/badge/skills/ashermahonin/agentic-skills/cicd-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.00052 | $0.00467 |
| Opus 5 | $0.00026 | $0.00234 |
| Sonnet 5 | $0.00010 | $0.00093 |
| Haiku 4.5 | $0.00005 | $0.00047 |
Grade A, and why
cicd-automation 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 10d 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 — 49 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CI/CD Automation
Purpose
You design delivery pipelines that are deterministic, observable, secure, and reversible. A good pipeline makes the release path boring in the best possible way.
Operational context
- Read
references/workflow.md. - Identify CI/CD platform, branch strategy, environments, artifact registry, secrets model, deployment target, quality gates, and rollback requirements.
- Verify current platform syntax, reusable workflow behavior, cache semantics, auth integrations, and deploy strategy documentation.
Safe change sequence
- Map source to build, test, scan, package, deploy, smoke-test, and rollback.
- Define what blocks release and what only reports.
- Choose release pattern: rolling, blue/green, canary, feature flags, manual approval, or protected environment.
- Implement pipeline files with pinned versions, scoped permissions, safe caching, concurrency, and environment-specific secrets.
- Validate with platform lint, dry-run where available, PR/MR run, artifact reproducibility, and rollback rehearsal.
Safety rules
- Use Context7 MCP for current cloud, Kubernetes, IaC, CI/CD, container, observability, security, network, API, CLI, provider, and configuration documentation whenever the task depends on external technology behavior.
Change record
Provide pipeline model, documentation validation status, YAML/scripts, secrets/auth notes, validation steps, rollback path, and assumptions.
Verification
- Do not publish artifacts before required gates pass.
- Do not mix build and deploy identities without a reason.
- Prefer OIDC or short-lived auth over static secrets.
- Pin actions/images/tools in production pipelines.
- Keep logs useful without leaking secrets.
Handoff
For container image work, pair with container-platforms. For cloud deploy targets, add cloud-operations. For Kubernetes deploys, add kubernetes-operations. For pipeline secrets, add security-secrets.
References
references/workflow.mdfor CI/CD structure, release patterns, and validation checklist.
What ships with it
2 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.
- 10d ago First seen · 49 lines · 52 tokens per session scan A 07f485ebf925
cicd-automation is a skill published in the GitHub repository ashermahonin/agentic-skills (10 stars, last pushed 17d ago), licensed MIT. It adds 52 tokens to every session and 467 once invoked, about $0.0003 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
import-prom-rule
Bulk import of a Prometheus alert rule YAML file (create a whole set of rules at once). Dedicated to handling a remote URL or local YAML text, automatically parsing the three formats groups / a plain rules array / a single rule. ⚠️ Do not use this skill for single-rule creation — when the user describes a single alert…
chinese-git-workflow
A reference for configuring Git with Chinese code-hosting services such as Gitee, Coding.net, GitLab China, and CNB, including SSH, HTTPS, credentials, CI, and repository mirroring.
configure-env-variables
Configures environment variables for Power Pages site settings to support ALM across environments. Creates environment variable definitions in Dataverse, guides the user through linking site settings to those variables via the Power Pages Management app, adds the variables to the solution, and generates a…
atmos-profiles
Atmos profiles: profile directories, --profile and ATMOSPROFILE activation, profile merge behavior, environment switching, and routing profile-specific auth/toolchain/config overrides.
webhook-management
Configure and validate CCAM webhook targets across supported chat, incident, automation, and generic providers. Use when listing provider requirements, creating or updating a target, scoping it to alert rules, sending a test notification, reviewing delivery history, or deleting a target.
monorepo-management
Master monorepo management with Turborepo, Nx, and pnpm workspaces to build efficient, scalable multi-package repositories with optimized builds and dependency management. Use when setting up monorepos, optimizing builds, or managing shared dependencies.