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 agentmods add commands/varunk130/ai-workflow-playbooks/releasegit clone --depth 1 https://github.com/varunk130/ai-workflow-playbooksWrote 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/commands/varunk130/ai-workflow-playbooks/release)<a href="https://agentmods.dev/commands/varunk130/ai-workflow-playbooks/release"><img src="https://agentmods.dev/badge/commands/varunk130/ai-workflow-playbooks/release.svg" alt="Measured on agentmods" 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 | $0.00000 | $0.00113 |
| Opus 5 | $0.00000 | $0.00056 |
| Sonnet 5 | $0.00000 | $0.00023 |
| Haiku 4.5 | $0.00000 | $0.00011 |
Grade A, and why
release 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 5d 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.
What it actually says
Run the RELEASE stage of the AI Workflow Playbooks pipeline.
Load and execute:
playbooks/release-orchestration/PLAYBOOK.md- Staged rollout with pre-launch checklist and go/no-go gates
Follow the pre-launch checklist:
- All tests pass
- Security scan is clean
- Documentation is updated
- Monitoring and alerting are configured
- Rollback procedure is verified
Determine go/no-go. If go, execute the release plan with appropriate staging (canary → percentage rollout → full release). Verify post-launch success criteria.
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.
- 5d ago First seen · 14 lines · 0 tokens per session scan A d4498a773c75
release is a command published in the GitHub repository varunk130/ai-workflow-playbooks (2 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 113 tokens. 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 commands, from other repositories
land-a-job
Workflow recipe — go after a specific role end to end by chaining 4 skills: decode the JD, research the company, tailor your application, and prep the interview.
ship-a-feature
Workflow recipe — take a feature idea from fuzzy brief to launch plan by chaining 5 skills.
ship-an-mcp-server
Workflow recipe — make your product agent-usable by chaining 4 skills, spec to pricing.
close-the-quarter
Workflow recipe — turn the quarter's raw numbers into a leadership story and board deck by chaining 4 skills.
rescue-an-account
Workflow recipe — diagnose an at-risk customer and build the full save play through to renewal by chaining 4 skills.
setup-context
Set up your Skill Memory — a pm-context.md every skill reads so outputs come back tailored to you.