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 zacharygcook/agent-skills --skill staged-script-rolloutgit clone --depth 1 https://github.com/zacharygcook/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/zacharygcook/agent-skills/staged-script-rollout)<a href="https://agentmods.dev/skills/zacharygcook/agent-skills/staged-script-rollout"><img src="https://agentmods.dev/badge/skills/zacharygcook/agent-skills/staged-script-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/zacharygcook/agent-skills/staged-script-rollout"><img src="https://agentmods.dev/badge/skills/zacharygcook/agent-skills/staged-script-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.00077 | $0.01277 |
| Opus 5.5 | $0.00031 | $0.00511 |
| Sonnet 5.5 | $0.00015 | $0.00255 |
| Haiku 4.5 | $0.00008 | $0.00128 |
Grade A, and why
staged-script-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 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 — 127 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Staged Script Rollout
Activation Gate
Use this skill only when BOTH conditions are true:
- The task is about actively operating or planning the rollout of a script through staged execution.
- The user makes that rollout intent explicit with language such as:
- "roll this out"
- "stage the rollout"
- "run the dry run, then a limited live run"
- "take this through dry run / live run"
- "ramp this script"
- "operate this script against production"
- "run this live safely"
If those conditions are not both true, do not use this skill.
Permission to make live calls is not enough. A user saying "you may run live ZoomInfo/Firecrawl/API calls," "run a small E2E test," or "smoke test the pipeline" is still not a staged-script-rollout request unless they explicitly ask for staged rollout/ramp sequencing.
Non-Triggers
Do not use this skill for:
- Implementing a new script unless the user explicitly asks to roll it out now.
- Revising an existing script unless the user explicitly asks to run or stage it now.
- Code review.
- General pipeline investigation.
- Test writing or test fixing.
- CI debugging.
- Refactoring.
- Adding safety checks, dry-run flags, audit output, or rollback support.
- Reading docs or explaining how a script works.
- Running ordinary local validation commands such as Ruff, pytest, or schema checks.
- Running a bounded E2E smoke test or pipeline probe.
- Debugging a failed live run after the fact.
- Noticing that a script touches HubSpot, PhoneBurner, Postgres, Firecrawl, ZoomInfo, or another external system.
For those tasks, follow the normal repo instructions and only mention staged rollout as an optional next step if it is directly useful.
Intended Use
When explicitly activated, use this skill for scripts that can mutate:
- HubSpot
- PhoneBurner
- shared Postgres mirrors
- other external systems or production-like state
The skill is about execution sequencing and operator commands, not general script development.
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.
- 1mo ago First seen · 127 lines · 77 tokens per session scan A e5b880d1b8ac
staged-script-rollout is a skill published in the GitHub repository zacharygcook/agent-skills (2 stars, last pushed 3mo ago), licensed MIT. It adds 77 tokens to every session and 1,277 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-08-31.
Other skills, from other repositories
cloud-sql-basics
This file generates or explains Cloud SQL resources. Use this file when the user asks to create a Cloud SQL instance or database for MySQL, PostgreSQL, or SQL Server. Cloud SQL manages third-party MySQL, PostgreSQL, and SQL Server instances as resources in Cloud SQL. For example, when Cloud SQL creates an open-source…
moai-platform-database-cloud
Cloud database platform specialist covering Neon (serverless PostgreSQL), Supabase (PostgreSQL 16 with real-time), and Firebase Firestore (NoSQL with offline sync). Use when choosing or setting up cloud databases.
dsql
Build with Aurora DSQL — manage schemas, execute queries, handle migrations, diagnose query plans, diagnose cluster performance, load data, and develop applications with a serverless, distributed SQL database. Covers IAM auth, multi-tenant patterns, MySQL-to-DSQL and PostgreSQL-to-DSQL schema conversion, foreign key…
sql-optimizer
Analyzes SQL queries for missing indexes, N+1 patterns, suboptimal joins, and full table scans. Interprets EXPLAIN, detects anti-patterns, rewrites queries. Triggers on: "optimize this query", "slow query", "add indexes", "explain plan", "N+1 query", "why is this query slow".
aws-rds
Amazon RDS is AWS's managed relational database service: it provisions MySQL, PostgreSQL, MariaDB, Oracle, SQL Server and Aurora databases and handles backups, patching and failover. Use this skill with the AWS CLI to create a Multi-AZ instance, an Aurora Serverless v2 cluster, read replicas, snapshots and…
backup-recovery
Design and verify backups and restoration for owned databases, files and application state. Use when preparing recovery, migrating data or testing backups; protect the source and prove restore into an isolated destination before calling recovery ready.