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 0xDarkMatter/claude-mods --skill ci-cd-opsgit clone --depth 1 https://github.com/0xDarkMatter/claude-modsWrote 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/0xdarkmatter/claude-mods/ci-cd-ops)<a href="https://agentmods.dev/skills/0xdarkmatter/claude-mods/ci-cd-ops"><img src="https://agentmods.dev/badge/skills/0xdarkmatter/claude-mods/ci-cd-ops.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.1 | $0.00066 | $0.02735 |
| Opus 5 | $0.00033 | $0.01367 |
| Sonnet 5 | $0.00013 | $0.00547 |
| Haiku 4.5 | $0.00007 | $0.00274 |
Grade A, and why
ci-cd-ops 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 7d 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 — 332 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CI/CD Operations
Comprehensive patterns for continuous integration, delivery, and deployment using GitHub Actions, release automation tools, and testing pipelines.
GitHub Actions Quick Reference
Workflow File Anatomy
name: CI # Display name in Actions tab
on: # Trigger events
push:
branches: [main]
pull_request:
branches: [main]
permissions: # GITHUB_TOKEN scope (least privilege)
contents: read
pull-requests: write
concurrency: # Prevent duplicate runs
group: ${{ github.workflow }}-${{ github.ref }}
cancel-in-progress: true
env: # Workflow-level environment variables
NODE_VERSION: "20"
jobs:
test:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
- uses: actions/setup-node@v4
with:
node-version: ${{ env.NODE_VERSION }}
cache: npm
- run: npm ci
- run: npm test
Core Syntax Elements
| Element | Purpose | Example |
|---|---|---|
on |
Event triggers | push, pull_request, schedule |
jobs.<id>.runs-on |
Runner selection | ubuntu-latest, self-hosted |
jobs.<id>.needs |
Job dependencies | needs: [build, lint] |
jobs.<id>.if |
Conditional execution | if: github.event_name == 'push' |
jobs.<id>.strategy.matrix |
Parallel variants | node-version: [18, 20, 22] |
jobs.<id>.environment |
Deployment target | environment: production |
jobs.<id>.permissions |
Token scope | contents: write |
steps[*].uses |
Use an action | uses: actions/checkout@v4 |
steps[*].run |
Run a command | run: npm test |
steps[*].env |
Step environment | env: { CI: true } |
Trigger Decision Tree
| Scenario | Trigger | Config |
|---|---|---|
| Run tests on every PR | pull_request |
branches: [main] |
| Deploy on merge to main | push |
branches: [main] |
| Release on version tag | push |
tags: ['v*'] |
| Nightly builds | schedule |
cron: '0 2 * * *' |
| Manual deployment | workflow_dispatch |
inputs: { environment: ... } |
| Called by another workflow | workflow_call |
inputs:, secrets: |
| On PR label change | pull_request |
types: [labeled] |
| On issue comment | issue_comment |
types: [created] |
| On release published | release |
types: [published] |
| On package push | registry_package |
types: [published] |
What ships with it
5 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.
- 7d ago First seen · 332 lines · 66 tokens per session scan A 605fb27cca59
ci-cd-ops is a skill published in the GitHub repository 0xDarkMatter/claude-mods (32 stars, last pushed 14d ago), licensed MIT. It adds 66 tokens to every session and 2,735 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-30.
Other skills, from other repositories
deploy
GitHub Actions deployment: workflows, releases, GHCR, CI/CD with safety gates. Triggers: deploy, release, workflow.
ci-cd-pipeline-patterns
Comprehensive CI/CD pipeline patterns skill covering GitHub Actions, workflows, automation, testing, deployment strategies, and release management for modern software delivery.
land-and-deploy
Merge PR, wait for CI, verify deploy, run canary. The complete landing pipeline.
finalize
Finalize orphaned recordings - stop processes, compress, push to orphan branch. TRIGGERS - finalize recording, stop asciinema, orphaned recording.
pipeline-digest
Daily release-pipeline digest with a change gate — reports which plugins are pending release, whether main's CI is green, and which branches went stale, and notifies the operator only when that state actually moved since the last run. Use when the operator asks "what moved in the pipeline", "anything to ship"…
land-and-deploy
Merge PR, wait for CI, verify deploy, run canary. The complete landing pipeline.