Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/ericrisco/rsc-harnessnpx agentmods add skills/ericrisco/rsc-harness/github-actionsWrote 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/ericrisco/rsc-harness/github-actions)<a href="https://agentmods.dev/skills/ericrisco/rsc-harness/github-actions"><img src="https://agentmods.dev/badge/skills/ericrisco/rsc-harness/github-actions/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/ericrisco/rsc-harness/github-actions"><img src="https://agentmods.dev/badge/skills/ericrisco/rsc-harness/github-actions.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Rogue Agent · line 73 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
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.00081 | $0.03413 |
| Opus 5.5 | $0.00032 | $0.01365 |
| Sonnet 5.5 | $0.00016 | $0.00683 |
| Haiku 4.5 | $0.00008 | $0.00341 |
Grade A, and why
github-actions 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 — 245 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub Actions CI/CD
A workflow is config that runs on an event. Before you write a single step, decide three things: which events fire the workflow, what permissions the token needs, and where credentials come from. Get those wrong and you have a fast pipeline that leaks secrets or a secure one nobody can trigger. Everything after that — checkout, install, test, build — is just steps.
This skill owns the workflow layer — the .github/workflows/*.yml files, their triggers, jobs, matrix, caching, secret/OIDC handling, environments and deploy gates. Route the rest out:
| Not this skill | Goes to | Because |
|---|---|---|
The Dockerfile, image build strategy |
../docker/SKILL.md |
The workflow may call docker build; designing the image is not this skill. |
| Branching model, PR hygiene, merge vs rebase, commit conventions | ../git-workflow/SKILL.md |
That is the source-control model, not the CI config layer. |
| Release readiness checklist, changelog, the shipping decision | ../ship/SKILL.md |
Whether to release is a decision; this skill only automates the mechanics. |
| Blue/green, canary, rollback theory | ../deployment/SKILL.md |
Actions triggers the deploy; the strategy is deployment's. |
| Choosing the host and its deploy primitives | ../vercel/SKILL.md, ../aws-essentials/SKILL.md |
Actions triggers the deploy; the host owns the target. |
| Triaging SAST/CVE findings, threat modeling | ../secure-coding/SKILL.md |
This skill runs a scanner as a job; it does not interpret the report. |
Decide the trigger first
Pick the event(s) for each job class before writing YAML — the trigger decides what context and secrets the run gets.
| Event | Use it for | Why |
|---|---|---|
pull_request |
lint, test, build-check | Runs on the merge ref; from forks it gets no secrets (safe). |
push (to main) |
deploy, publish artifacts, build the release | The trusted ref with full secrets/OIDC. |
workflow_dispatch |
manual ops, one-off backfills, manual deploys | Human-triggered with inputs; auditable. |
schedule (cron) |
nightly builds, dependency audits, cache warmers | Cron in UTC; no human in the loop. |
release / push tags |
publish to a registry, cut a GitHub Release | Fires on the tag, not every commit. |
workflow_call |
reusable workflow invoked by others | Library of jobs; never runs on its own. |
pull_request_target |
label/comment bots that need write on forks | Runs trusted with secrets — never check out PR head here. |
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.
- 1mo ago First seen · 245 lines · 81 tokens per session scan A 9b5ced270b3c
github-actions is a skill published in the GitHub repository ericrisco/rsc-harness (237 stars, last pushed yesterday), licensed MIT. It adds 81 tokens to every session and 3,413 once invoked, about $0.0003 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-09-03.
Other skills, from other repositories
CI Pipeline Optimizer
Optimize CI test pipelines through intelligent test splitting, parallelization, caching strategies, and selective test execution based on code changes.
workflow-setup
Configures GitHub Actions CI/CD workflows for testing, linting, and deployment. Use when setting up automation for a Python, Rust, or TypeScript project.
GitHub Actions CI Testing
Setting up and optimizing test pipelines in GitHub Actions with caching, parallel execution, matrix builds, and test result reporting.
github-actions-workflows
GitHub Actions workflow patterns for CI/CD including matrix builds, reusable workflows, secrets management, and caching strategies. Use when setting up or optimizing GitHub Actions pipelines.
ci-cd
Create and debug GitHub Actions CI/CD pipelines: workflow authoring, matrix builds, caching, secrets, deployment steps.
Verification & Quality Assurance
Comprehensive truth scoring, code quality verification, and automatic rollback system with 0.95 accuracy threshold for ensuring high-quality agent outputs and codebase reliability.