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 Goodsmileduck/claude-registry --skill github-actions-pipelinesgit clone --depth 1 https://github.com/Goodsmileduck/claude-registryWrote 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/goodsmileduck/claude-registry/github-actions-pipelines)<a href="https://agentmods.dev/skills/goodsmileduck/claude-registry/github-actions-pipelines"><img src="https://agentmods.dev/badge/skills/goodsmileduck/claude-registry/github-actions-pipelines.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.00103 | $0.04011 |
| Opus 5 | $0.00051 | $0.02005 |
| Sonnet 5 | $0.00021 | $0.00802 |
| Haiku 4.5 | $0.00010 | $0.00401 |
Grade A, and why
github-actions-pipelines scanned grade A with 1 finding 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.
Unrestricted tool accesslowExcessive agency
A wildcard tool grant or "run any command" leaves no least-privilege boundary at all.
The default-deny rule: **never use self-hosted runners on public repos with `pull_request` from forks.** Fork PRs can run arbitrary code on the runner, which then has network access to your internal infra. Downgraded: this mod is about security review, or the phrase is quoted, so it is likely naming the pattern rather than instructing it.
How it starts
The opening of the file, as written. The whole thing — 338 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub Actions Pipelines
When to invoke
Symptoms:
Not authorized to perform: sts:AssumeRoleWithWebIdentityfrom a GitHub Actions job that's "supposed to use OIDC."Error: google-github-actions/auth failed with: failed to generate Google Cloud federated token.- A required status check is stuck "Expected — Waiting for status to be reported" on PRs that touched unrelated paths.
- Secrets are
null/ empty in a workflow triggered by a fork PR. - A reusable workflow can't see the caller's secrets.
- Two deploys to the same environment race each other and the older one wins.
actions/cachereports a hit but the build still re-installs everything.- A workflow runs untrusted PR code with
pull_request_targetand has secrets — security audit needs a verdict.
The trap this prevents: treating GitHub Actions as "just YAML." The privilege model, trigger semantics, and branch-protection interactions have non-obvious failure modes that look like "the action is broken" but are actually misconfiguration.
Cross-cutting rules
These apply to every section below.
- Pin third-party actions to a commit SHA, not a floating tag. See supply chain for the format. First-party
actions/*/aws-actions/*/google-github-actions/*can use major-version tags; everything else pins by SHA. - Default
permissions:to least-privilege. Addpermissions: contents: readat the workflow root and elevate per-job only what's needed. A repo's "default workflow permissions" setting can bereadorread-and-writeorg-wide — don't rely on it; be explicit. - Never check out and execute fork code from
pull_request_target. See the pull_request_target rule. - Verify current action versions before recommending YAML. First-party actions (
aws-actions/*,google-github-actions/*,actions/*) ship breaking major versions on their own cadence and training data lags. Before writing YAML, query the action's README via Context7 (/aws-actions/configure-aws-credentials,/actions/cache, etc.) to confirm the current major and any protocol changes. - Skipped jobs are not passing jobs. A required check that's skipped (via
paths:,if:, or matrix-exclude) reports nothing to branch protection. See path-filter trap.
What ships with it
3 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 · 338 lines · 103 tokens per session scan A 850ee703fa60
github-actions-pipelines is a skill published in the GitHub repository Goodsmileduck/claude-registry (1 stars, last pushed 1mo ago), licensed MIT. It adds 103 tokens to every session and 4,011 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it A with 1 finding (unrestricted tool access). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
cicd-expert
Expert-level CI/CD with GitHub Actions, Jenkins, deployment pipelines, and automation. Use when the user mentions CI/CD, GitHub Actions, Jenkins, GitLab CI, deployment, or automation, or when the task involves CI/CD Fundamentals, Pipeline Design, Workflow Basics, or Docker Build and Push.
cicd-agent
CI/CD pipeline design and review — GitHub Actions, pipeline best practices, secrets management, deployment strategies, and release automation.
devops-best-practices
Opinionated production-grade DevOps defaults for Terraform, Kubernetes, CI/CD, Docker, cloud security, observability, cost, and disaster recovery. ALWAYS use when generating, reviewing, or modifying any infrastructure code, Kubernetes manifests (Deployment, Service, StatefulSet, Helm, Kustomize), Terraform (.tf…
deployment-pipeline-design
Design multi-stage CI/CD pipelines with approval gates, security checks, and deployment orchestration. Use this skill when designing zero-downtime deployment pipelines, implementing canary rollout strategies, setting up multi-environment promotion workflows, or debugging failed deployment gates in CI/CD.
gitlab-ci-patterns
Build GitLab CI/CD pipelines with multi-stage workflows, caching, and distributed runners for scalable automation. Use when implementing GitLab CI/CD, optimizing pipeline performance, or setting up automated testing and deployment.
bazel-build-optimization
Optimize Bazel builds for large-scale monorepos. Use when configuring Bazel, implementing remote execution, or optimizing build performance for enterprise codebases.