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 laurigates/claude-plugins --skill ci-workflowsgit clone --depth 1 https://github.com/laurigates/claude-pluginsWrote 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/laurigates/claude-plugins/ci-workflows)<a href="https://agentmods.dev/skills/laurigates/claude-plugins/ci-workflows"><img src="https://agentmods.dev/badge/skills/laurigates/claude-plugins/ci-workflows/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/laurigates/claude-plugins/ci-workflows"><img src="https://agentmods.dev/badge/skills/laurigates/claude-plugins/ci-workflows.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00041 | $0.01273 |
| Opus 5.5 | $0.00016 | $0.00509 |
| Sonnet 5.5 | $0.00008 | $0.00255 |
| Haiku 4.5 | $0.00004 | $0.00127 |
Grade A, and why
ci-workflows 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 14d 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 — 150 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CI Workflow Standards
When to Use This Skill
| Use this skill when... | Use a sibling skill instead when... |
|---|---|
| You need the canonical GitHub Actions workflow shapes (container build, test, release) | You want to audit or install workflows end-to-end as an interactive workflow — use configure-workflows |
You are checking whether existing .github/workflows/*.yml follows the documented conventions |
You want pre-built reusable callers wired up — use configure-reusable-workflows |
| Another skill needs to cite the standard workflow structure | The user asked you to actually create or repair CI workflows |
Version: 2025.1
Standard GitHub Actions workflows for CI/CD automation.
Display name convention
Every workflow's name: follows <Domain>: <Action> [<target>] so the GitHub Actions sidebar groups related workflows alphabetically. Quote the value because YAML treats : inside an unquoted scalar as a key separator. See .claude/rules/workflow-naming.md for the canonical rule, the active domain list, and the cross-workflow rename procedure. Mirror the pattern in any workflow you scaffold here.
Required Workflows
Full YAML, key features, and prerequisites for each file live in references/workflow-templates.md — read it when citing, diffing against, or scaffolding a specific workflow.
| # | Workflow | File | Status |
|---|---|---|---|
| 1 | Container Build | .github/workflows/container-build.yml |
Required if Dockerfile |
| 2 | Release Please | .github/workflows/release-please.yml |
Required |
| 3 | ArgoCD Auto-merge | .github/workflows/argocd-automerge.yml |
Optional |
| 4 | Test | .github/workflows/test.yml |
Recommended |
| 5 | Claude Auto-Fix | .github/workflows/claude-auto-fix.yml |
Optional |
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.
- 14d ago Changed · -230 lines b1dc95e67603
- 25d ago Changed · +11 tokens per session b13df97a67e0
- 1mo ago First seen · 380 lines · 30 tokens per session scan A 2cf9f5b2c292
ci-workflows is a skill published in the GitHub repository laurigates/claude-plugins (60 stars, last pushed yesterday), licensed MIT. It adds 41 tokens to every session and 1,273 once invoked, about $0.0002 per session on Opus 5.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
ci-log-interpretation
Use this skill when reading or analyzing CI logs from a Shopware GitHub Actions workflow to figure out why a build failed — phrases like "why did CI fail", "what broke the build", "check the pipeline", "interpret these logs", "debug this red build" — or whenever raw run logs, job logs, or check annotations from a…
code-review
CI code-review lane for a GitHub pull request. High-signal correctness and maintainability findings only, scoped out of security when a security lane exists. Use when: 'CI code review', 'claude-review lane', '/review:code-review', or a reusable workflow invokes the org code-review plugin command.
github-logs-analyze
Analyze GitHub Actions failure logs.
cicd
CI/CD pipeline patterns and deployment strategies for automated, reliable software delivery. Use when the user asks to design a build pipeline, choose a deployment model (blue-green, canary, rolling), configure environment promotion, manage build artifacts, implement zero-downtime deployments, set up quality gates, or…
codebase-documenter
Scaffold project documentation (README, ARCHITECTURE, API, CODECOMMENTS) from templates with documented standards. Use when bootstrapping docs for a new or under-documented codebase.
npm-trusted-publishing
Set up or debug npm Trusted Publishing (OIDC) from GitHub Actions. Handles permissions, metadata validation, and provenance.