Borrowing it
Nothing to install: this file belongs to WaniWani-AI/sdk. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/WaniWani-AI/sdk/main/.agents/skills/deploy-prod/SKILL.mdgit clone --depth 1 https://github.com/WaniWani-AI/sdkWrote 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/waniwani-ai/sdk/deploy-prod)<a href="https://agentmods.dev/skills/waniwani-ai/sdk/deploy-prod"><img src="https://agentmods.dev/badge/skills/waniwani-ai/sdk/deploy-prod.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector pass
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.00079 | $0.00913 |
| Opus 5 | $0.00039 | $0.00456 |
| Sonnet 5 | $0.00016 | $0.00183 |
| Haiku 4.5 | $0.00008 | $0.00091 |
Grade A, and why
deploy-prod 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 8d 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 — 125 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Production Deployment PR
Create a production deployment pull request following these steps.
This skill assumes the repo deploys via a long-lived
deploy/prodbranch and a GitHub Action that tagsdeploy/prodon merge. If the repo doesn't use that flow, stop and tell the user.
Pre-flight Checks
-
Check working directory is clean
git status --porcelainIf not clean, warn the user and stop.
-
Fetch latest from origin
git fetch origin -
Check if main is up to date with origin/main
git rev-parse main git rev-parse origin/mainIf they differ, warn the user that local main is not up to date.
-
Check if there are changes to deploy
git log origin/deploy/prod..origin/main --onelineIf no commits, inform the user there's nothing new to deploy.
Determine Version
-
Get today's date in format
YYYY-MM-DD -
Check existing tags for today
git tag -l "YYYY-MM-DD-r*" -
Calculate next release number
- If no tags for today exist, use
r1 - If
YYYY-MM-DD-r1exists, user2, etc.
- If no tags for today exist, use
-
Format version:
YYYY-MM-DD-r{N}(e.g.,2026-01-19-r1) -
Get latest release tag for the compare link
git tag -l "*-r*" --sort=-version:refname | head -1
Gather Changes for PR Description
-
Get commits between deploy/prod and main
git log origin/deploy/prod..origin/main --oneline -
Filter to only include commits with GitHub PR links
- Only include commits that contain a PR reference like
(#123)or(https://github.com/.../pull/123) - Exclude commits without PR links (these are likely bad merges that should have been squashed)
- Format each included commit as a bullet point with the PR link
Example of what to include:
- feat: add user dashboard (#142) - fix: resolve authentication bug (#138)Example of what to EXCLUDE (no PR link):
- Only include commits that contain a PR reference like
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.
- 8d ago First seen · 125 lines · 79 tokens per session scan A 6b78beec1d1c
deploy-prod is a skill published in the GitHub repository WaniWani-AI/sdk (17 stars, last pushed yesterday), licensed MIT. It adds 79 tokens to every session and 913 once invoked, about $0.0004 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-08-30.
Other skills, from other repositories
publish-site
Versioned site deploys to GitHub/Cloudflare/Netlify Pages.
batch
Research and plan a large-scale change, then execute it in parallel across 5–30 isolated worktree agents that each open a PR.
github
GitHub via gh CLI: PRs, issues, reviews, repos, auth.
release-jetbrains
Use when releasing the Kilo JetBrains plugin -- resolve a version ("next rc" or explicit), run the prepare workflow, edit and commit a filtered human-readable changelog on the release PR, then watch publish to completion.
git-wrapup
Land working-tree changes as logical commits — the work grouped by concern, topped by a release commit (version bump, changelog, regenerated artifacts) and an annotated tag. Verify, commit, tag. Stops at "committed and tagged locally" — no push, no publish. The release-and-publish skill picks up from here. Distilled…
release-and-publish
Ship a release end-to-end across every registry the project targets (npm, MCP Registry, GitHub Releases for .mcpb bundles, GHCR). Runs the final verification gate, pushes commits and tags, then publishes to each applicable destination. Assumes git wrapup (version bumps, changelog, commit, annotated tag) is already…