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 flurdy/agent-skills --skill watch-actions-rolloutgit clone --depth 1 https://github.com/flurdy/agent-skillsWrote 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/flurdy/agent-skills/watch-actions-rollout)<a href="https://agentmods.dev/skills/flurdy/agent-skills/watch-actions-rollout"><img src="https://agentmods.dev/badge/skills/flurdy/agent-skills/watch-actions-rollout/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/flurdy/agent-skills/watch-actions-rollout"><img src="https://agentmods.dev/badge/skills/flurdy/agent-skills/watch-actions-rollout.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.00059 | $0.02851 |
| Opus 5 | $0.00030 | $0.01425 |
| Sonnet 5 | $0.00012 | $0.00570 |
| Haiku 4.5 | $0.00006 | $0.00285 |
Grade A, and why
watch-actions-rollout 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 3d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
allowed-tools: "Read,Write,AskUserQuestion,Skill,Bash(~/.agents/skills/watch-actions-rollout/scripts/run-jobs.sh:*),Bash(~/.agents/skills/watch-actions-rollout/scripts/default-head-sha.sh:*),Bash(gh api:*),Bash(gh pr vie How it starts
The opening of the file, as written. The whole thing — 228 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Watch GitHub Actions Rollout
Watch a post-merge GitHub Actions deploy to staging, then smoke-test the change once it lands —
the generic, GitHub-Actions-based cousin of /watch-release (which is hardwired to a specific
kubectl/CircleCI/Flux stack). Built for client repos with extensive CD workflows.
Chains naturally after /ready-to-merge: merge → watch the deploy job → confirm the change is live.
Usage
/watch-actions-rollout # deploy of latest origin/main commit, smoke staging
/watch-actions-rollout 6790 # resolve via PR number (uses its merge commit)
/watch-actions-rollout <sha> # specific commit
/watch-actions-rollout --run 28440286944 # specific workflow run id
/watch-actions-rollout --prod # allow a read-only prod smoke (safety-gated, see below)
/watch-actions-rollout --no-smoke # watch the deploy only, skip the smoke test
Procedure
Phase 0 — Load config (optional)
Read .claude/rollout.yaml at the repo root if present. Recognised keys (all optional):
workflow: CMS Pages # deploy workflow name to watch
gating_job: Deploy blc-uk # substring of the job that gates the target env
staging_url: https://legacy.staging.bluelightcard.co.uk
prod_url: https://www.bluelightcard.co.uk
smoke: |
Load /en logged-out, capture the first Amplitude "Page Viewed" request,
assert login_state=logged_out is in the event user properties.
Anything missing is inferred or asked for below. Never require the file — it's a convenience for repos you watch repeatedly.
Phase 1 — Resolve the commit and run
Determine the target commit and run (first match wins):
--run {run_id}→ resolve the run and its exact commit directly:
Recordgh run view {run_id} --json databaseId,name,workflowName,headSha,status,conclusion,eventheadShaas{sha}and retain the returned run and workflow identity. Skip the commit-based run listing below.- PR number → use its merge commit (
gh pr view {n} --json mergeCommit --jq .mergeCommit.oid). - Explicit sha → use it unchanged.
- No target → resolve the latest default-branch commit:
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.
- 3d ago First seen · 228 lines · 59 tokens per session scan A a8a77b347079
watch-actions-rollout is a skill published in the GitHub repository flurdy/agent-skills (9 stars, last pushed 4d ago), licensed MIT. It adds 59 tokens to every session and 2,851 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-08.
Other skills, from other repositories
ci
Configure Ginkgo for continuous integration — the recommended CLI flag set and the rationale for each flag (-r -p --randomize-all --randomize-suites --fail-on-pending --fail-on-empty --keep-going --cover --race --trace --json-report --timeout --poll-progress-after/-interval), invoking via go run to pin the CLI to…
migrate-vstest-to-mtp
Use this skill before answering, planning, or editing whenever .NET tests or CI are switching from VSTest to Microsoft.Testing.Platform (MTP), or an MTP migration behaves differently. Triggers include "switch from VSTest"; MSTest/NUnit/xUnit MTP enablement; OutputType=Exe only for test projects in…
playwright-ci
Production-ready CI/CD configurations for Playwright — GitHub Actions, GitLab CI, CircleCI, Azure DevOps, Jenkins, Docker, parallel sharding, reporting, code coverage, and global setup/teardown.
playwright-testing
E2E testing with Playwright - Page Objects, cross-browser, CI/CD.
ci-maintenance-workflow
CI and GitHub Actions maintenance workflows — fix a failing test from a CI URL, fix a failing smoke test, add @pytest.mark.slow markers to slow tests, or review a PR against agent-checkable standards. Use when user asks to fix a failing test, fix a smoke test, mark slow tests, or review a PR. Trigger when the user…
test-setup
Scaffold the test framework and CI/CD pipeline for the project's engine. Creates the tests/ directory structure, engine-specific test runner configuration, and GitHub Actions workflow. Run once during Technical Setup phase before the first sprint begins.