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 OpenLabor/openlabor --skill deploy-to-productiongit clone --depth 1 https://github.com/OpenLabor/openlaborWrote 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/openlabor/openlabor/deploy-to-production)<a href="https://agentmods.dev/skills/openlabor/openlabor/deploy-to-production"><img src="https://agentmods.dev/badge/skills/openlabor/openlabor/deploy-to-production.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.1 | $0.00007 | $0.00150 |
| Opus 5 | $0.00003 | $0.00075 |
| Sonnet 5 | $0.00001 | $0.00030 |
| Haiku 4.5 | $0.00001 | $0.00015 |
Grade A, and why
Deploy to Production 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 4d 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
Deploy to Production
Manage production deployments
You are a deployment engineer.
Objective
Execute safe, zero-downtime production deployments.
Process
- Verify all CI checks pass on the release branch
- Run smoke tests against staging
- Deploy using rolling update strategy
- Monitor error rates and latency for 15 minutes post-deploy
- Rollback immediately if error rate exceeds 1%
Guidelines
- Never deploy on Fridays or before holidays
- Announce deployments in the team channel
- Keep deployment artifacts versioned and reproducible
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.
- 4d ago First seen · 31 lines · 7 tokens per session scan A 8e85e19f33dc
Deploy to Production is a skill published in the GitHub repository OpenLabor/openlabor (4 stars, last pushed 6d ago), licensed MIT. It adds 7 tokens to every session and 150 once invoked, about $0.0000 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
shieldcn-badges
Create polished shieldcn README badges, badge groups, charts, headers, sponsors grids, and full README hero sections. Use when a user wants shadcn/ui-styled badges, Shields.io replacement, npm/GitHub/CI/status badges, download charts, README header banners, contributor/sponsor images, or README Studio guidance.…
ci-cd
CI/CD pipeline expert for GitHub Actions, GitLab CI, Jenkins, and deployment automation.
terraform
Terraform IaC expert for providers, modules, state management, and planning.
workflow-setup
Configures GitHub Actions CI/CD workflows for testing, linting, and deployment. Use when setting up automation for a Python, Rust, or TypeScript project.
memory-ci-capture
Synthesize GitHub delivery context into a concise Basic Memory project update. Use in CI after bm ci collect prepares a ProjectUpdateContext; return only structured AgentSynthesis JSON for bm ci publish.
devops-expert
Expert-level DevOps practices, culture, automation, and continuous delivery. Use when the user mentions CI/CD, automation, infrastructure, or culture, or when the task involves DevOps Culture or Culture & Process.