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 Vimalk0703/shipworthy --skill production-readinessgit clone --depth 1 https://github.com/Vimalk0703/shipworthyWrote 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/vimalk0703/shipworthy/production-readiness)<a href="https://agentmods.dev/skills/vimalk0703/shipworthy/production-readiness"><img src="https://agentmods.dev/badge/skills/vimalk0703/shipworthy/production-readiness/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/vimalk0703/shipworthy/production-readiness"><img src="https://agentmods.dev/badge/skills/vimalk0703/shipworthy/production-readiness.svg" alt="Reviewed on agentmods" width="80" 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.00049 | $0.04396 |
| Opus 5 | $0.00024 | $0.02198 |
| Sonnet 5 | $0.00010 | $0.00879 |
| Haiku 4.5 | $0.00005 | $0.00440 |
Grade A, and why
production-readiness 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 10d 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 — 415 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Production Readiness
How to Use This Checklist
Go through each section before your first production deployment. Items are marked:
- MUST — Do this before launch. Skipping it creates real risk (security holes, data loss, legal exposure).
- SHOULD — Do this within the first week. Your app works without it, but you're flying blind or leaving value on the table.
- NICE — Do this when you can. Improves quality of life but won't break anything if delayed.
1. Security Checklist
MUST: Secrets Are in Environment Variables, Not in Code
Plain language: None of your passwords, API keys, or secret tokens should be written directly in your code files. They should be in your .env file (which never gets uploaded to GitHub) and set in your hosting provider's settings for the live site.
Technical detail:
- Grep your codebase for hardcoded secrets:
grep -r "sk_live\|sk_test\|password\|secret" --include="*.ts" --include="*.js" --include="*.tsx" --include="*.jsx" src/ - Verify
.envis in.gitignore - Check git history for accidentally committed secrets:
git log --all --oneline -- .env - If secrets were ever committed, rotate ALL of them immediately
- Use
lib/env.tsvalidation pattern (see environment-setup skill)
MUST: Authentication Is Working Correctly
Plain language: People can sign up, log in, and log out. Pages that should be private (like dashboards or settings) can't be seen by someone who isn't logged in. If someone types in a URL for a page they shouldn't see, they get redirected to the login page.
Technical detail:
- Test login flow end-to-end (email/password and each social provider)
- Test logout clears session completely
- Verify middleware protects all private routes
- Test that API endpoints reject unauthenticated requests with 401
- Test that API endpoints reject unauthorized requests with 403
- Test password reset flow
- Verify session expiry works (sessions don't last forever)
- If using JWT: tokens have reasonable expiry (not 30 days)
- If using cookies:
httpOnly,secure,sameSiteflags are set
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.
- 10d ago First seen · 415 lines · 49 tokens per session scan A 9b3c1c9c3342
production-readiness is a skill published in the GitHub repository Vimalk0703/shipworthy (7 stars, last pushed 5mo ago), licensed MIT. It adds 49 tokens to every session and 4,396 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
hedgehog-planning-intake
Use on any core for first-run planning intake — Phase 0 runs the vendored BMAD-METHOD planning shelf, shared by every core, and Phase 1 (mining 04-prd.md into intent records plus the Add-ons/sync-and-remote-entities decision) is full-stack-app's and pwa-app's shared procedure — identical mechanics, a different…
bmad-product-brief
Create, update, or validate a product brief. Use when the user wants help producing, editing, or validating a brief.
bmad-deep-recon
Decision-grade research, three ways: draft a deep-research prompt for the user to run in their own tool (ChatGPT, Gemini, Grok, Perplexity, …), process a finished research report — file it, distill a succinct cited summary with metadata that downstream skills consume without reprocessing — or run the research here…
hedgehog
Use when the user writes the word "Hedgehog" anywhere in a request, or has agreed to install the Hedgehog build discipline in a project that does not have it yet. Hedgehog builds prose as well as code — articles, essays, blog posts, tweets, threads, newsletters, announcements, and marketing or product copy of any…
conventional-commits
Use when uncommitted changes need to be split into atomic, conventional commits ordered for review. Triggers on "commit this", "make commits", "clean up commits", "commit the changes". In Hedgehog, each Loop step is already meant to be its own commit — this skill matters most when a Correction Protocol fast-forward…
hedgehog-contributing
Use when the user wants to contribute a fix or roadmap item back to the Hedgehog project itself (skyf0xx/hedgehog) rather than their own project. Triggers on "let's fix that in Hedgehog", "I want to contribute", "let's pick up a roadmap item", or when tweaker offers this at the end of a build and the user says yes.…