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/rand/cc-polymath/discover-cicdnpx skills add rand/cc-polymath --skill discover-cicdgit clone --depth 1 https://github.com/rand/cc-polymathWrote 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/rand/cc-polymath/discover-cicd)<a href="https://agentmods.dev/skills/rand/cc-polymath/discover-cicd"><img src="https://agentmods.dev/badge/skills/rand/cc-polymath/discover-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.00045 | $0.00420 |
| Opus 5 | $0.00023 | $0.00210 |
| Sonnet 5 | $0.00009 | $0.00084 |
| Haiku 4.5 | $0.00005 | $0.00042 |
Grade A, and why
discover-cicd 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 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.
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
Cicd Skills Discovery
Provides automatic access to comprehensive cicd skills.
When This Skill Activates
This skill auto-activates when you're working with:
- CI/CD
- GitHub Actions
- GitLab CI
- automation
- pipelines
- continuous integration
- deployment automation
- build systems
- Make
- CMake
- Gradle
- Maven
- Bazel
- compilation
- incremental builds
Available Skills
Quick Reference
The Cicd category contains 12 skills across 2 subcategories:
CI/CD (4 skills):
- cd-deployment-patterns
- ci-optimization
- ci-security
- ci-testing-strategy
Build Systems (8 skills): See ../build-systems/INDEX.md
Load Full Category Details
Read ../cicd/INDEX.md Read ../build-systems/INDEX.md
Progressive Loading
This gateway skill enables progressive loading:
- Level 1: Gateway loads automatically (you're here now)
- Level 2: Load category INDEX.md for full overview
- Level 3: Load specific skills as needed
Usage Instructions
- Auto-activation: This skill loads automatically when Claude Code detects cicd work
- Browse skills: Run
Read ../cicd/INDEX.mdfor full category overview - Load specific skills: Use bash commands above to load individual skills
Next Steps: Run Read ../cicd/INDEX.md to see full category details.
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 · 66 lines · 45 tokens per session scan A 4d09d5a477d1
discover-cicd is a skill published in the GitHub repository rand/cc-polymath (140 stars, last pushed 6mo ago), licensed MIT. It adds 45 tokens to every session and 420 once invoked, about $0.0002 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
aws-cloudformation-task-ecs-deploy-gh
Provides patterns to deploy ECS tasks and services with GitHub Actions CI/CD. Use when building Docker images, pushing to ECR, updating ECS task definitions, deploying ECS services, integrating with CloudFormation stacks, configuring AWS OIDC authentication for GitHub Actions, and implementing production-ready…
pentest-supply-chain
Software supply chain security — dependency confusion, CI/CD pipeline attacks, lockfile integrity, and build artifact verification.
glab-cli
GitLab CLI (glab) reference and workflow for repository, merge request, issue, CI/CD, release, and API operations across GitLab.com and self-managed or dedicated instances. Use when Codex needs to run or explain glab commands, usually by relying on the current glab context first, and only falling back to git remote -v…
zb-release-pipeline
Generate a GitHub Actions pipeline that builds a zb (Zero Dependencies Builder) project and publishes a GitHub Release with the produced JAR. Use whenever the user wants CI/CD, a build pipeline, a release workflow, or GitHub Actions for a zb-based Java project — phrases like "set up GitHub Actions for this zb…
fastly-fiddle
Use when testing VCL against real Fastly edge infrastructure, writing assertion-based Fiddle tests, producing shareable fiddle URLs for bug reproductions, running VCL integration tests in CI, linting VCL remotely via the Fiddle API, or working with clientFetch/events/originFetches test expressions.
buildkite-api
This skill should be used when the user asks to "call the Buildkite API", "use the REST API", "write a GraphQL query", "set up webhooks", "automate Buildkite", "integrate with Buildkite programmatically", "write a script that calls Buildkite", "handle webhook events", "paginate API results", or "authenticate with the…