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 intent-to-specgit 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/intent-to-spec)<a href="https://agentmods.dev/skills/vimalk0703/shipworthy/intent-to-spec"><img src="https://agentmods.dev/badge/skills/vimalk0703/shipworthy/intent-to-spec.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.00055 | $0.01502 |
| Opus 5 | $0.00028 | $0.00751 |
| Sonnet 5 | $0.00011 | $0.00300 |
| Haiku 4.5 | $0.00006 | $0.00150 |
Grade A, and why
intent-to-spec 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 8d 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 — 143 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Intent-to-Spec
Purpose
Bridge the gap between "user says what they want" and "code starts flowing." Without a spec, AI-generated code drifts from intent. With a heavyweight spec process, non-technical users bounce. This skill generates a lightweight specification in a single pass — fast enough to be invisible, structured enough to anchor the work.
When This Skill Fires
- YES: "Build me an invoice app", "Add Stripe payments", "Create a dashboard", "Implement user auth"
- NO: "Fix the typo", "Change the button color", "Add a health endpoint", "Rename this variable"
- NO: A spec already exists in
.shipworthy/specs/for this feature
Tier Behavior
Builder Tier (Non-Technical Users)
- Generate the spec silently — do not show it to the user
- Save it to
.shipworthy/specs/without discussion - Use the spec internally to guide your work
- The user should never know a spec was written — they just see better results
- If something is genuinely ambiguous (e.g., "build me an app" with zero context), ask ONE clarifying question, not five
Maker Tier
- Generate the spec and show a brief summary (3-4 bullets) before proceeding
- "Here's what I'll build: [bullets]. Sound right?"
- Save to
.shipworthy/specs/after implicit or explicit approval - Do not wait for formal sign-off — if the user doesn't object, proceed
Engineer Tier
- Generate the full spec and present it for review
- Wait for explicit approval before proceeding to brainstorming/planning
- Save to
.shipworthy/specs/after approval
Spec Generation Process
This is a single-pass process. Do NOT turn it into a multi-step interrogation.
Step 1: Capture Intent
Read the user's request and extract:
- What they want (in their own words — preserve their language)
- Who it's for (end users, internal team, themselves)
- Why it matters (what problem does this solve)
If the request is too vague to build anything (e.g., "make an app"), ask ONE clarifying question:
"What's the main thing this app should do? I'll figure out the rest."
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.
- 8d ago First seen · 143 lines · 55 tokens per session scan A e1e88e50ddd1
intent-to-spec is a skill published in the GitHub repository Vimalk0703/shipworthy (7 stars, last pushed 5mo ago), licensed MIT. It adds 55 tokens to every session and 1,502 once invoked, about $0.0003 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.md 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.…