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-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-rollout)<a href="https://agentmods.dev/skills/flurdy/agent-skills/watch-rollout"><img src="https://agentmods.dev/badge/skills/flurdy/agent-skills/watch-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-rollout"><img src="https://agentmods.dev/badge/skills/flurdy/agent-skills/watch-rollout.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 Excessive Agency · line 9 Skill selects an external model or provider that may use a different account or billing plan than the operator expects. Undisclosed model switches can cause unexpected cost or quota consumption.Fix: Remove the model/provider override or disclose it prominently and require explicit operator approval before invoking an external coding CLI or billed model.
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.00033 | $0.00539 |
| Opus 5 | $0.00016 | $0.00269 |
| Sonnet 5 | $0.00007 | $0.00108 |
| Haiku 4.5 | $0.00003 | $0.00054 |
Grade A, and why
watch-rollout 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 2d 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 — 65 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Choose Rollout Watcher
Select the deployment stack, then delegate the entire rollout watch to its specialist skill. This router does not inspect deployments, run commands, schedule polling, or combine stack-specific safety rules.
Usage
/watch-rollout # ask which implemented stack to watch
/watch-rollout actions [arguments] # GitHub Actions
/watch-rollout github [arguments] # alias for actions
/watch-rollout flux [arguments] # CircleCI + FluxCD
Legacy target forms remain valid. For example, /watch-rollout 6790, /watch-rollout <sha>, and
/watch-rollout --run 28440286944 ask for the stack and then pass the original arguments to the
selected implementation.
Route selection
Recognize an explicit first argument as follows:
| Selector | Delegate |
|---|---|
actions, github, github-actions |
watch-actions-rollout |
flux, circleci-flux |
watch-flux-rollout |
When a selector matches, remove only that first argument. Forward all remaining arguments unchanged. Invoke the mapped skill immediately without prompting.
Always ask when no explicit stack selector is supplied. Use AskUserQuestion with exactly these
implemented choices:
- GitHub Actions — invoke
watch-actions-rolloutwith every original argument. - CircleCI + FluxCD — invoke
watch-flux-rolloutwith every original argument.
Do not infer a stack from repository files or remember a previous answer. Do not list planned or unimplemented providers. Cloudflare Workers/Pages, Google Cloud Build, and other stacks may be added later as specialist skills plus one explicit row and prompt option here.
Delegation contract
Invoke exactly one specialist through Skill and stop. The specialist owns argument validation,
revision identity, configuration, confirmation, polling, smoke tests, terminal behavior, and error
reporting. Never reproduce or relax those rules in this router.
Direct specialist invocation remains supported:
What ships with it
1 file 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.
- 2d ago Changed · -155 lines · -32 tokens per session 488c80e1ce14
- 7d ago First seen · 220 lines · 65 tokens per session scan A ffce6547819c
watch-rollout is a skill published in the GitHub repository flurdy/agent-skills (9 stars, last pushed 4d ago), licensed MIT. It adds 33 tokens to every session and 539 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-09-03.
Other skills, from other repositories
chinese-git-workflow
A reference for configuring Git with Chinese code-hosting services such as Gitee, Coding.net, GitLab China, and CNB, including SSH, HTTPS, credentials, CI, and repository mirroring.
baby-sit
Monitor a GitHub pull request until CI is green, diagnose failures, and rerun only evidence-backed flaky GitHub Actions jobs.
atmos-hooks
Atmos hooks: lifecycle events, hook kinds, command/store/git/security hooks, step/steps hooks, when: conditions, scoping and overrides, toolchain integration, --skip-hooks, and Atmos Pro/local output.
atmos-pro
Atmos Pro setup and workflows: settings.pro, GitHub OIDC, affected and inventory uploads, stack locks, pro commit, workflow dispatch, merge queues, and drift detection.
start-temps-cluster
Start (or restart) a local multi-node Temps cluster using Docker-in-Docker — one control plane + 3 worker nodes, each a privileged DinD container running its own dockerd + temps agent, wired with the real multi-host overlay (VXLAN, computecidr allocation) via tools/dev-cluster/ in whichever checkout/worktree you run…
pr-watch
Local PR watcher. Monitors CI status, automatically fixes failing checks by reading failure logs and applying targeted fixes, then optionally merges when all checks pass. Local CLI analog to Claude Code's cloud auto-fix feature.