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 JayRHa/AgentSkills --skill github-actions-buildergit clone --depth 1 https://github.com/JayRHa/AgentSkillsWrote 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/jayrha/agentskills/github-actions-builder)<a href="https://agentmods.dev/skills/jayrha/agentskills/github-actions-builder"><img src="https://agentmods.dev/badge/skills/jayrha/agentskills/github-actions-builder/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/jayrha/agentskills/github-actions-builder"><img src="https://agentmods.dev/badge/skills/jayrha/agentskills/github-actions-builder.svg" alt="Reviewed on agentmods" width="80" 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.00109 | $0.01765 |
| Opus 5.5 | $0.00044 | $0.00706 |
| Sonnet 5.5 | $0.00022 | $0.00353 |
| Haiku 4.5 | $0.00011 | $0.00177 |
Grade A, and why
github-actions-builder 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 1mo 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 — 107 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub Actions Builder
Overview
Author production-grade GitHub Actions workflows that are fast, deterministic, and secure by default.
Keywords: github actions, workflow, ci, cd, ci/cd, .github/workflows, jobs, steps, runs-on, matrix, build matrix, strategy, fail-fast, cache, actions/cache, setup-node, setup-python, setup-go, secrets, GITHUB_TOKEN, permissions, OIDC, environments, reusable workflow, workflow_call, composite action, concurrency, artifacts, upload-artifact, deploy, release, pinning SHA, dependabot.
This skill covers the full lifecycle: choosing triggers, structuring jobs, caching dependencies correctly, fanning out across a matrix, passing secrets safely, gating deployments with environments, and factoring shared logic into reusable or composite workflows. Always prefer the patterns and pinning rules in references/best-practices.md and validate output structure with scripts/validate_workflow.py.
Workflow
-
Clarify intent. Identify: project language/runtime, the events that should trigger CI (push, pull_request, tag, schedule, manual), and whether deployment is in scope. If the user only says "add CI", default to lint + test on
pushto the default branch and onpull_request. -
Pick triggers (
on:). Usepull_requestfor validation andpush(filtered to the default branch) to avoid double-runs on PR branches. Addworkflow_dispatchfor manual runs andtagsfilters for release pipelines. See the trigger matrix inreferences/best-practices.md. -
Set top-level defaults. Always add
permissions:(least privilege, defaultcontents: read) andconcurrency:to cancel superseded runs. Pin a sensibletimeout-minuteson every job. -
Structure jobs. Split lint, test, and build/deploy into separate jobs so failures are isolated and parallel. Use
needs:to express ordering. Gate deploy jobs onif: github.ref == 'refs/heads/main' && github.event_name == 'push'. -
Add a matrix when relevant. Fan out across runtime versions and OSes with
strategy.matrix. Setfail-fast: falsefor test matrices so one failure does not cancel the rest. Useinclude/excludefor targeted combinations. Seeexamples/node-matrix-ci.md.
What ships with it
7 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.
- 1mo ago First seen · 107 lines · 109 tokens per session scan A a0a6241e34ff
github-actions-builder is a skill published in the GitHub repository JayRHa/AgentSkills (12 stars, last pushed 2mo ago), licensed MIT. It adds 109 tokens to every session and 1,765 once invoked, about $0.0004 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-08-31.
Other skills, from other repositories
devops-engineer
Use when setting up CI/CD pipelines, containerizing applications, or managing infrastructure as code. Invoke for pipelines, Docker, Kubernetes, cloud platforms, GitOps.
autonomous-loops
Patterns and architectures for autonomous Claude Code loops — from simple sequential pipelines to RFC-driven multi-agent DAG systems.
deployment-patterns
Deployment workflows, CI/CD pipeline patterns, Docker containerization, health checks, rollback strategies, and production readiness checklists for web applications. Use when setting up deployment infrastructure or planning releases.
mcp-dependency-review
Statically review MCP configuration for mutable package references before approval or CI, without executing discovered MCP servers. Use when reviewing .mcp.json, Cursor, VS Code, Claude, Windsurf, or other repo-scoped MCP config.
quality-scan
Run a scoped, read-only quality scan and report exact-candidate evidence, failures and frozen debt. Use for an ad-hoc gate sweep or release preparation; a static scan is not full release acceptance.
vercel
Inspect and manage the user's Vercel websites, web apps, projects, and deployments. Use to read build and runtime logs, investigate production errors and failed deployments, check deployment status, and deploy projects through Vercel's official MCP server.