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/jansenanalytics/claudex/ci-cdnpx skills add JansenAnalytics/claudex --skill ci-cdgit clone --depth 1 https://github.com/JansenAnalytics/claudexWhat 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.00028 | $0.00528 |
| Opus 5 | $0.00014 | $0.00264 |
| Sonnet 5 | $0.00006 | $0.00106 |
| Haiku 4.5 | $0.00003 | $0.00053 |
Grade A, and why
ci-cd 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 2d 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
Create and debug GitHub Actions CI/CD pipelines: workflow authoring, matrix builds, caching, secrets, deployment steps.
When to Use
- Setting up CI/CD for a new project
- Writing GitHub Actions workflows
- Debugging failed CI runs
- Optimizing build times and caching
- Adding deployment steps
- Configuring matrix builds
Scripts
scripts/generate-workflow.sh <template> [options]
Generate a GitHub Actions workflow from templates. Templates: node, python, docker, rust, go.
bash scripts/generate-workflow.sh node --name "CI" --node-version "18,20,22"
bash scripts/generate-workflow.sh python --name "Test" --python-version "3.11,3.12"
bash scripts/generate-workflow.sh docker --name "Build" --registry ghcr.io
scripts/lint-workflow.sh [path]
Lint GitHub Actions workflow YAML files for common errors (invalid keys, bad expressions, missing required fields).
bash scripts/lint-workflow.sh .github/workflows/ci.yml
bash scripts/lint-workflow.sh .github/workflows/ # lint all
scripts/cache-optimizer.sh [path]
Analyze workflows and suggest caching improvements (dependency caches, build caches, artifact strategies).
bash scripts/cache-optimizer.sh .github/workflows/ci.yml
References
references/actions-syntax.md— GitHub Actions workflow syntax quick referencereferences/common-workflows.md— Ready-to-use workflow snippetsreferences/matrix-strategies.md— Matrix build patterns and fail-fast configsreferences/caching-patterns.md— Caching strategies by ecosystem
Tips
- Always pin action versions to full SHA for security (e.g.,
actions/checkout@v4minimum) - Use
concurrencygroups to cancel redundant runs on push - Cache
node_modules/.venv/target/for faster builds - Use
if: always()for cleanup steps that must run - Set
timeout-minuteson jobs to prevent hung builds
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.
- 2d ago First seen · 65 lines · 28 tokens per session scan A dc4400f4c3eb
ci-cd is a skill published in the GitHub repository JansenAnalytics/claudex (5 stars, last pushed 2mo ago), licensed MIT. It adds 28 tokens to every session and 528 once invoked, about $0.0001 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
ci-cd-workflows
Guide for GitHub Actions workflows, test orchestration, parallel testing, adapter builds, releases, and CI/CD configuration. Use when working with .github/workflows/, versions.json, or troubleshooting CI issues.
deployment
Import, release, and manage Falcon Fusion workflow definitions in a CID. TRIGGER when user asks to import a workflow, release a workflow version, list existing workflows, check for duplicates, or manage workflow definitions. DO NOT TRIGGER for writing YAML (use authoring), executing workflows, or monitoring (use…
github-workflow-automation
Advanced GitHub Actions workflow automation with AI swarm coordination, intelligent CI/CD pipelines, and comprehensive repository management.
ci-cd
Flutter CI/CD 파이프라인 가이드라인. 코드 서명, Fastlane, Codemagic, GitHub Actions, 스토어 배포, 버전 관리 자동화.
ci-cd-pipeline
Design and implement CI/CD pipelines for automated testing and deployment.
cicd-agent
CI/CD pipeline design and review — GitHub Actions, pipeline best practices, secrets management, deployment strategies, and release automation.