Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add samsantosb/ship-it/plugin install ship-itWrote 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/samsantosb/ship-it/create-product)<a href="https://agentmods.dev/skills/samsantosb/ship-it/create-product"><img src="https://agentmods.dev/badge/skills/samsantosb/ship-it/create-product/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/samsantosb/ship-it/create-product"><img src="https://agentmods.dev/badge/skills/samsantosb/ship-it/create-product.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.00052 | $0.00961 |
| Opus 5 | $0.00026 | $0.00481 |
| Sonnet 5 | $0.00010 | $0.00192 |
| Haiku 4.5 | $0.00005 | $0.00096 |
Grade A, and why
create-product 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 9d 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 — 65 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: create-product
Entry point of the pipeline. Anyone — founder, dev, designer, PM, whoever — brings raw material and leaves with a product document that /create-tasks can split into technical cards. The pipeline makes no assumption about who writes product scope or where: the document is produced by interview, not by role. Respond in the conversation language (docs/agents/language.md; unset → the user's language).
Load before acting: ${CLAUDE_PLUGIN_ROOT}/shared/workflow-context.md, ${CLAUDE_PLUGIN_ROOT}/shared/sparring.md, and ${CLAUDE_PLUGIN_ROOT}/shared/guardrails.md — this skill writes product docs and may publish tracker items; the loading contract applies.
Accepted input: free text in the argument, a path to a rough doc, "this conversation", or nothing at all (start from zero).
Process
1 — Gather context and resolve roles
Collect the raw material: the argument, the referenced file, or the current conversation. If a repo is connected, read related docs and code before asking anything. List what the material already answers — those questions are skipped.
Resolve the Tracker role now, per ${CLAUDE_PLUGIN_ROOT}/shared/workflow-context.md (batched question if unresolved) — config questions happen before the sparring session starts, never in the middle of it.
2 — Sparring session
Run ${CLAUDE_PLUGIN_ROOT}/shared/sparring.md over the idea. Minimum topic checklist: the problem, who it's for, measurable success criteria, scope in/out, constraints, and the riskiest assumption. Depth is proportional to ambiguity — a well-written draft might need 3 questions; a one-liner might need 20. Stop when the sparring completion criteria hold: you could sketch the solution and a QA could write a test plan without guessing.
3 — Synthesize the document
Fixed template. Section headers are fixed English tokens (stable for /create-tasks to parse); the content inside them is written in the user's language. Product-level only — technical detail (files, tests, stacks) belongs to /create-tasks:
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.
- 9d ago First seen · 65 lines · 52 tokens per session scan A 65e20b0acdf0
create-product is a skill published in the GitHub repository samsantosb/ship-it (23 stars, last pushed 1mo ago), licensed MIT. It adds 52 tokens to every session and 961 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-30.
Other skills, from other repositories
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
monorepo-management
Master monorepo management with Turborepo, Nx, and pnpm workspaces to build efficient, scalable multi-package repositories with optimized builds and dependency management. Use when setting up monorepos, optimizing builds, or managing shared dependencies.