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/vimalk0703/shipworthy/using-shipworthynpx skills add Vimalk0703/shipworthy --skill using-shipworthygit 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/using-shipworthy)<a href="https://agentmods.dev/skills/vimalk0703/shipworthy/using-shipworthy"><img src="https://agentmods.dev/badge/skills/vimalk0703/shipworthy/using-shipworthy.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.00042 | $0.03641 |
| Opus 5 | $0.00021 | $0.01820 |
| Sonnet 5 | $0.00008 | $0.00728 |
| Haiku 4.5 | $0.00004 | $0.00364 |
Grade A, and why
using-shipworthy 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 6d 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 — 276 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Using Shipworthy
You are enhanced with the Shipworthy plugin — a comprehensive set of skills that help you produce production-quality systems, not just prototypes.
Core Thesis
Vibe coding is how you start; engineering is what keeps it alive.
Your job is to apply invisible discipline: enforce engineering principles automatically so the user never has to think about process. They describe what they want; you ensure it's built correctly.
Non-Negotiable Defaults (Apply On Every Project)
These are not suggestions. Apply them automatically without asking:
- NEVER use
console.log— use a structured logger (pinofor Node.js,loggingfor Python,slogfor Go). This includes server startup messages. If no logger is installed, install one as a first step. - ALWAYS use Zod for input validation (TypeScript/JavaScript). Install it (
npm install zod) before writing any route handler. For Python, use Pydantic. For Go, use thevalidatorpackage. - ALWAYS configure test coverage — add
@vitest/coverage-v8(or equivalent) and acoveragescript in package.json. For Python:pytest-cov. For Go:go test -cover. - ALWAYS set up a linter — install ESLint (TypeScript/JS), Ruff (Python), or
golangci-lint(Go) and add alintscript. Use a strict config. - NEVER use
: anyin TypeScript. Useunknownand narrow with type guards. For catch blocks, usecatch (err: unknown)and narrow:if (err instanceof Error). - ALWAYS use proper HTTP status codes — 201 for creation, 204 for deletion, 400 for validation, 401 for auth, 403 for authz, 404 for not found, 409 for conflict, 429 for rate limit.
- ALWAYS use a database (SQLite minimum) — never use in-memory arrays/objects for data that should persist. In-memory data disappears on server restart.
Priority Hierarchy
When making decisions, follow this priority order:
- User instructions — always highest priority
- Architecture specification (
.shipworthy/architecture.md) — project-specific constraints - Skill instructions — engineering best practices encoded in skills
- Default behavior — your base training
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.
- 6d ago First seen · 276 lines · 42 tokens per session scan A 5dc5c8a41e97
using-shipworthy is a skill published in the GitHub repository Vimalk0703/shipworthy (7 stars, last pushed 4mo ago), licensed MIT. It adds 42 tokens to every session and 3,641 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-core-design
Use on full-stack-app and landing-page alike only when neither shipped core fits a project that is still building something real — picks the stack and designs the layer sequence for it, and writes .hedgehog/core.yaml. Invoked by the planner agent as Phase 0's third outcome, after the vendored BMAD shelf has run; don't…
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…
inbound-triage
Maintainer-only. Use when triaging inbound GitHub issues and pull requests on skyf0xx/hedgehog — "triage the issues", "check the PRs", "review inbound", "what's in the queue". Reads each item read-only, judges it for security and for whether it is real, then fixes and closes or comments and closes. Not part of the…
bmad-product-brief
Create, update, or validate a product brief. Use when the user wants help producing, editing, or validating a brief.
bmad-revendor
Maintainer-only. Use when re-vendoring vendor-skills/BMAD/ against a newer BMAD-METHOD commit — "update BMAD", "re-vendor BMAD", "bump the BMAD pin". Not part of the Hedgehog discipline a consuming project copies; this only applies to the Hedgehog repo itself.
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…