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 lucasheriques/shipmate --skill product-betsgit clone --depth 1 https://github.com/lucasheriques/shipmateWrote 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/lucasheriques/shipmate/product-bets)<a href="https://agentmods.dev/skills/lucasheriques/shipmate/product-bets"><img src="https://agentmods.dev/badge/skills/lucasheriques/shipmate/product-bets/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/lucasheriques/shipmate/product-bets"><img src="https://agentmods.dev/badge/skills/lucasheriques/shipmate/product-bets.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.00104 | $0.02230 |
| Opus 5 | $0.00052 | $0.01115 |
| Sonnet 5 | $0.00021 | $0.00446 |
| Haiku 4.5 | $0.00010 | $0.00223 |
Grade A, and why
product-bets 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 — 76 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Product bets — decide, construct, test, operate
When to use
Any time the question is "should we build this?", "what exactly do we build?", or "how do we keep making good bets week after week". Four procedures, used together or alone: separating the instinct from the idea (before committing), constructing the bet with Proven-Better-New (what to copy, improve, and isolate), testing it as a Minimum Idea State (before building), and running the weekly roadmap operating system (after launch). Core stance: your instinct is right ~95% of the time; your specific idea is right at best ~25% — so fall in love with the instinct and kill ideas cheaply, often, and without grief.
The procedure
1. Separate the instinct from the idea
- Write both down separately. Instinct = the deep human truth you feel ("getting a taxi should be easier"). Idea = the specific implementation ("order a taxi by SMS"). The instinct survives dead ideas; number the ideas as attempts.
- Check the body of water before the boat: pick the market first. Criteria: market entry potential (available, not crowded) · proven business (clear path to revenue) · room to innovate (the best are mature markets that are secretly growth markets) · long-term macro tailwinds. "If you choose the right body of water, most boats will float."
- Apply the B+ test: B+ ideas are good enough to get funding, customers, and hope — and never good enough to be great. Ask: would your smartest friends invest their own money? Are you pursuing this out of desperation? B+ is the enemy of A; kill it before it consumes the quarter.
- Distrust false positives: smart investors or big partners wanting in is NOT signal. True signal is felt instantly ("f*** yeah", not "this is close").
2. Construct the bet with Proven-Better-New
- Proven — copy what your target audience already loves, to the pixel. Operational test: "I could rebuild that same interface with the same features, put it in front of the same people, and get the same reaction." Get your PhD in deconstructing the proven products with heat, ideally proven on the same platform for the same audience. You haven't earned the right to change what already works. Best to market beats first to market.
- Better — only objectively better counts: half the price, no download, one click instead of five — improvements 10 out of 10 users say "yes" to. The classic error: what you think is Better is actually New. Better rarely wins alone except on a platform shift.
- New — exactly ONE novel element, isolated so it can be tested (and fail) separately without sinking the product. "All New fails" — assume it, so a failure is clean data, not a catastrophe.
- Placement rules: on a platform shift, ship Proven + Better with no New — the platform IS the New (and it's the single best place to build). In a mature market, you need a genuine New vein to earn trial. Never bet on New without Proven underneath (fool's gold: unrepeatable one-off wins).
- Guard the other flank: PBN over-applied yields derivative B+ products. Copy to de-risk the base, then pursue actual quality/magic on top — the bar is a product you treasure.
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 · 76 lines · 104 tokens per session scan A 540d310a84c8
product-bets is a skill published in the GitHub repository lucasheriques/shipmate (4 stars, last pushed 1mo ago), licensed MIT. It adds 104 tokens to every session and 2,230 once invoked, about $0.0005 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
solo-failures
Understand why startups fail — the most common failure modes, anti-patterns, and how to avoid them, backed by data from 101 founder interviews.
solo-analyze
Evaluate a startup idea against real patterns from 101 founder interviews.
solo-growth
Get data-backed growth and marketing recommendations for your business.
solo-roast
Get your startup plan roasted with data — Garry Tan style.
solo-patterns
Browse and search the startup pattern database (11 categories, 80+ patterns).
solo-playbook
Get a data-backed step-by-step playbook for any startup goal.