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/stefan-stepzero/shipkit/shipkit-scale-readynpx skills add stefan-stepzero/shipkit --skill shipkit-scale-readygit clone --depth 1 https://github.com/stefan-stepzero/shipkitWhat 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.00032 | $0.04703 |
| Opus 5 | $0.00016 | $0.02351 |
| Sonnet 5 | $0.00006 | $0.00941 |
| Haiku 4.5 | $0.00003 | $0.00470 |
Grade A, and why
shipkit-scale-ready 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 2d 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 — 476 lines — stays where its author put it; the contents beside it link to each section on GitHub.
shipkit-scale-ready - Scale Readiness Audit
Purpose: Ensure your production system can handle growth and be operated reliably.
Who this is for: Teams with traction — you've launched, you have users, now you need to harden for scale.
Prerequisite: Preflight passed. This skill assumes MVP-level production readiness already exists.
When to Invoke
User triggers:
- "Ready to scale"
- "Scale readiness check"
- "Production hardening"
- "Post-MVP audit"
- "We have traction, what should we fix?"
- "Enterprise readiness"
Workflow position:
- After MVP launch and user traction
- Before scaling marketing/growth efforts
- Before enterprise customers
- When transitioning from "it works" to "it's robust"
The Two Tiers
| Tier | When | Focus |
|---|---|---|
| 🔶 Growth | Have traction, scaling up | Can handle 10x users, can debug prod issues |
| 🏢 Enterprise | Big customers, high stakes | Compliance, SLAs, operational maturity |
Default audit covers Growth tier. Enterprise tier on request or if context indicates enterprise customers.
Process
Completion Tracking
After determining scope, create tasks per audit category:
TaskCreatefor each applicable category (Security/DB, Observability/Perf, Reliability/Ops, Code Maturity, Compliance)TaskCreate: "Merge all subagent results"TaskCreate: "Write scale-readiness.json"TaskCreate: "Archive previous audit (if full audit)"
TaskUpdate each task to in_progress when starting it, completed when done.
Subagent results returning is NOT done — results must be merged, classified, and written to the JSON artifact. Do NOT skip the archive step.
Step 0: Verify Prerequisites
1. Check if preflight passed recently
- Read .shipkit/preflight.json
- If blockers exist: "Fix preflight blockers first — run /preflight"
2. Load project context
- .shipkit/stack.json — tech stack
- .shipkit/why.json — scale expectations
- .shipkit/architecture.json — key patterns
What ships with it
5 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.
- 2d ago First seen · 476 lines · 32 tokens per session scan A 71a673b959af
shipkit-scale-ready is a skill published in the GitHub repository stefan-stepzero/shipkit (1 stars, last pushed 1mo ago), licensed MIT. It adds 32 tokens to every session and 4,703 once invoked, about $0.0002 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-31.
Other skills, from other repositories
opencli-sitemap-author
Use when creating or maintaining OpenCLI site sitemaps: agent-facing navigation, page-state, action, workflow, API-reference, pitfall, and fallback knowledge for a website. Use after browser exploration discovers durable site context, when a sitemap is stale, or when promoting local site knowledge into the repo.
golden-rss
Use when testing the rss golden build.
omh-buzz
This is a Hermes-native buzz workflow skill.
omh-code-review
This is a Hermes-native code-review workflow skill.
redteam-api-detail-pack
Domain routing and boundary guidance for authorized API security testing, including BOLA/IDOR, authentication bypass, mass assignment, missing rate limits, and GraphQL issues. Use when a task belongs to the API testing domain and needs scope, evidence, pivot, or exit criteria.
redteam-postex-detail-pack
Domain routing and boundary guidance for authorized post-exploitation testing after initial access, including privilege escalation, persistence, lateral movement, data collection, and cleanup considerations. Use when a task belongs to the post-exploitation domain and needs scope, evidence, pivot, or exit criteria.