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 stealth-factory/skills --skill production-release-gatinggit clone --depth 1 https://github.com/stealth-factory/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/stealth-factory/skills/production-release-gating)<a href="https://agentmods.dev/skills/stealth-factory/skills/production-release-gating"><img src="https://agentmods.dev/badge/skills/stealth-factory/skills/production-release-gating/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/stealth-factory/skills/production-release-gating"><img src="https://agentmods.dev/badge/skills/stealth-factory/skills/production-release-gating.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.00191 | $0.04042 |
| Opus 5 | $0.00096 | $0.02021 |
| Sonnet 5 | $0.00038 | $0.00808 |
| Haiku 4.5 | $0.00019 | $0.00404 |
Grade A, and why
production-release-gating 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 11d 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.
a **deploy hook** (`curl "$DEPLOY_HOOK_URL"`), `wrangler deploy`, `flyctl deploy`, How it starts
The opening of the file, as written. The whole thing — 235 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Gating production deploys to real releases
By default, a push/merge to main deploys to production. With
semantic-release you usually want the
opposite: previews on feature branches, but production only on an actual
release (a versioned chore(release): commit / a published GitHub Release).
There are three ways to enforce that. They have names, not letters, so you can pick one by name and record it (see "pick the flow" below):
| Release-Triggered Deploy | Promotion Branch | Build-Skip Gate | |
|---|---|---|---|
| One-liner | CI runs the deploy when a Release publishes | a release fast-forwards a production branch the platform watches |
a script cancels non-release builds on the platform |
| Who deploys | a workflow you control (GKE, self-hosted, dispatchable, or a platform CLI) | the platform's native git integration, but only off production |
the platform auto-builds every push; the script vetoes |
| The gate | a published Release triggers the deploy; plain pushes deploy nothing | production only advances on a published Release; main = staging |
the script skips the build unless it's a release commit |
| Portability | any dispatchable target (must disable native push-deploy — see below) | any host with a configurable production branch (Vercel, Netlify, CF Pages) — most portable | Vercel/Netlify only (platform-specific script) |
| Template | release-production.yml |
promote-to-production.yml |
vercel-ignore.sh |
Decision rule:
- Want to keep the platform's native git deploys with zero platform-specific scripting? → Promotion Branch (set the production branch, promote on release). Most portable; the recommended default for Vercel/Netlify/CF Pages.
- You own the deploy (GKE/self-hosted/any dispatchable target, or you want CI to drive a platform CLI)? → Release-Triggered Deploy.
- Locked into a platform's push-deploy and can't add a branch/promotion? → Build-Skip Gate (the ignore script) as the fallback.
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.
- 11d ago First seen · 235 lines · 191 tokens per session scan A eabcc292dec8
production-release-gating is a skill published in the GitHub repository stealth-factory/skills (3 stars, last pushed 15d ago), licensed MIT. It adds 191 tokens to every session and 4,042 once invoked, about $0.0010 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-08-31.
Other skills, from other repositories
publish
Publish oh-my-opencode to npm by triggering the GitHub Actions publish workflow and verifying its artifacts. Ship-only: never runs pre-publish-review or re-reviews merged code unless the user explicitly asks. Argument: . Triggers: publish, release, deploy, npm publish.
pre-publish-review
Nuclear-grade 12-agent pre-publish release gate. Runs /get-unpublished-changes to detect all changes since last npm release, spawns up to 10 ultrabrain agents for deep per-change analysis, invokes /review-work (orchestrator manual QA plus one gate reviewer) for holistic review, and 1 oracle for overall release…
get-unpublished-changes
Compare HEAD with the latest published npm versions and list all unpublished changes by release layer. Triggers: unpublished changes, changelog, what changed, whats new.
lov-release-via-cicd
A release workflow for Node, Tauri, Vite, shell, and GitHub Release projects. It checks or configures automated versioning and publishing, including macOS signing and notarisation when relevant.
pdlc-ship
A software release workflow that runs tests, updates the version and change log, creates a Git tag, and starts CI/CD, the automated build and deployment process.
ci-cd-pipelines
When designing GitHub Actions workflows, optimizing pipeline speed, implementing deployment gates.