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 skills/arbazkhan971/godmode/deploynpx skills add arbazkhan971/godmode --skill deploygit clone --depth 1 https://github.com/arbazkhan971/godmodeWrote 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/arbazkhan971/godmode/deploy)<a href="https://agentmods.dev/skills/arbazkhan971/godmode/deploy"><img src="https://agentmods.dev/badge/skills/arbazkhan971/godmode/deploy.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.00033 | $0.02463 |
| Opus 5 | $0.00016 | $0.01231 |
| Sonnet 5 | $0.00007 | $0.00493 |
| Haiku 4.5 | $0.00003 | $0.00246 |
Grade A, and why
deploy 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 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -s http://localhost/healthz | jq .status How it starts
The opening of the file, as written. The whole thing — 276 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Deploy — Advanced Deployment Strategies
Activate When
- User invokes
/godmode:deploy - User says "deploy with zero downtime," "canary release," "blue-green deployment"
- User needs rollback strategy for a risky change
- Feature flags need orchestration for a complex rollout
- Database migrations or infrastructure changes require zero-downtime approach
- Godmode orchestrator detects high-risk changes during
/godmode:ship
Workflow
Step 1: Assess Deployment Context
Characterize the change and determine the correct deployment strategy:
DEPLOYMENT ASSESSMENT:
Change type: <application code | database migration | infrastructure | config | all>
Risk level: <LOW | MEDIUM | HIGH | CRITICAL>
Rollback complexity: <INSTANT | MINUTES | HOURS | DIFFICULT>
Change characteristics:
- [ ] Backward compatible (old code works with new data)
- [ ] Forward compatible (new code works with old data)
- [ ] Database schema changes involved
- [ ] API contract changes (breaking/non-breaking)
- [ ] Infrastructure changes (new services, topology)
- [ ] Feature flags available
- [ ] Stateful components affected (sessions, caches)
Current environment:
Step 2: Blue-Green Deployment
Two identical environments, instant switchover:
BLUE-GREEN DEPLOYMENT PLAN:
LOAD BALANCER → routes 100% to active environment
[BLUE env: v1.0 (live)] ←── current traffic
[GREEN env: v1.1 (idle)] ←── deploy here, then switch
Step 3: Canary Release
Route a small percentage of traffic to the new version:
CANARY RELEASE PLAN:
LOAD BALANCER (traffic splitting)
95% → [STABLE: v1.0, N instances]
5% → [CANARY: v1.1, 1 instance]
Gradually shift: 5% → 25% → 50% → 100% based on metrics
Step 4: Progressive Rollout
Percentage-based traffic shifting with automated gates:
PROGRESSIVE ROLLOUT PLAN:
| Stage | Traffic | Duration | Gate | Rollback |
|--|--|--|--|--|
| 1. Smoke | 0% (int) | 5 min | Auto | Auto |
| 2. Seed | 1% | 10 min | Auto | Auto |
| 3. Low | 5% | 15 min | Auto | Auto |
| 4. Med | 25% | 30 min | Manual | Auto |
| 5. High | 50% | 30 min | Manual | Auto |
| 6. Full | 100% | Monitor | Manual | Manual |
Gate criteria:
Auto gate: pass if all success metrics within threshold for full duration
Manual gate: auto gate + human approval required to proceed
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 · 276 lines · 33 tokens per session scan A 038ee4f82404
deploy is a skill published in the GitHub repository arbazkhan971/godmode (26 stars, last pushed 6d ago), licensed MIT. It adds 33 tokens to every session and 2,463 once invoked, about $0.0002 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-30.
Other skills, from other repositories
jobs-to-be-done
Discover what customers truly need by analyzing the "job" they hire your product to do. Use when the user mentions "customer discovery", "why customers churn", "what job does this solve", "competing against luck", "product-market fit", "switching behavior", "milkshake moment", or "functional vs emotional jobs". Also…
asc-subscription-localization
Bulk-localize subscription, subscription-group, and in-app purchase display names across App Store locales using asc, including API 4.4.1 version-scoped v2 resources. Use when filling or updating subscription/IAP names and descriptions without App Store Connect UI work.
scienceworld-growth-focuser
Use when you have planted a seed or need to track a plant's growth stage (sprouting, flowering, reproduction). Applies the 'focus on' action to a specific plant or biological entity to signal intent and monitor its development. Trigger after planting or when you need to observe life cycle progression in the…
ralph-specum-requirements
This skill should be used only when the user explicitly asks to use $ralph-specum-requirements, or explicitly asks Ralph Specum in Codex to run the requirements phase.
biome
Repository guidance for using Biome as the formatter, linter, and code quality tool within the hr-skills monorepo.
dashboard-builder
Build and manage recurring dashboard views of key metrics — set up daily/weekly monitoring with saved metrics and segments. Use when the user wants to create a recurring dashboard, set up KPI monitoring, or establish a baseline.