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/lucasheriques/shipmate/positioningnpx skills add lucasheriques/shipmate --skill positioninggit 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/positioning)<a href="https://agentmods.dev/skills/lucasheriques/shipmate/positioning"><img src="https://agentmods.dev/badge/skills/lucasheriques/shipmate/positioning.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 | $0.00074 | $0.01644 |
| Opus 5 | $0.00037 | $0.00822 |
| Sonnet 5 | $0.00015 | $0.00329 |
| Haiku 4.5 | $0.00007 | $0.00164 |
Grade A, and why
positioning 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 3d 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 — 63 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Positioning (Obviously Awesome)
When to use
Run this whenever you are defining or revising how a product/company is framed: category choice, hero copy, one-liner, pitch, competitive narrative. Also run it diagnostically when any weak-positioning symptom appears: current customers love it but new prospects can't figure out what it is; long sales cycles and low close rates; fast churn shortly after purchase; constant price pressure. Any one symptom means suspect the frame before the product.
The procedure
Mandatory ordering constraint: never run the chain backwards. Alternatives -> unique attributes -> value -> who cares -> market category -> (optional trend). Starting from features, a persona, or a category you picked at inception is how bad positioning happens. Each step's output is the next step's input.
- Start from the customers who love the product. List best-fit customers only: understood it fast, bought fast, didn't haggle, refer others. They define what the product actually is. If there aren't enough happy customers yet, stop — keep positioning deliberately broad and loose, sell wide, and wait for patterns. Don't tighten pre-product-market-fit.
- Assemble the deciders. Positioning is business strategy, not a marketing deliverable: the business owner must drive it, with one or two senior people per function (marketing, sales, product, success). Solo founder or agent-run? Fine — just make sure the output binds roadmap and pricing, not only copy.
- Name and drop the baggage. State explicitly how the product has always been framed ("we set out to build X, so we are X"). Customers carry none of that history. Get agreement to suspend it for the exercise.
- List true competitive alternatives. Ask: "what would our best customers do if we didn't exist?" Include spreadsheets, an intern, "nothing." Exclude rivals customers have never heard of, however closely you watch them. Rank by how common; cluster into 2-5 groups.
- Isolate unique attributes — with proof. Only capabilities the alternatives lack, and only what you can prove (data, third-party reviews, approved customer quotes — your own opinion is not proof). "Easy to use" without evidence doesn't count. Prefer consideration attributes (drive the buy) over retention attributes (drive renewal).
- Map attributes to value themes. For each attribute, ask "so what?" repeatedly until you reach a goal the customer already has (feature -> benefit -> value). Cluster into 1-4 themes. Positioning fronts the most critical value; it is not a feature catalog.
- Determine who cares a lot. Segment by easily identifiable traits that predict loving the value — tools they already use, how they sell, skills they lack — not demographics. Target as narrowly as possible while still covering near-term sales goals (sizing test: deals needed this year vs. companies in the segment). The segment must also have a specific, important, unmet need.
- Choose the market category — then the style. The category is a frame that silently sets assumed competitors, expected features, and price band; pick the frame where your strengths are assumed, not explained. Find candidates by abduction ("what kind of product has these features?"), adjacent fast-growing markets, and (cautiously) customer suggestions. Then pick one of the three styles (see reference below).
- Optionally layer a trend. Only on an already-clear category, only with a real product link. A trend says why now, never what you are.
- Capture it on the positioning canvas (fields below), then operationalize: sales story arc (problem -> today's gaps -> perfect world -> product-in-category -> value themes -> proof -> ask), one master messaging document to prevent drift, and roadmap + pricing realigned to the category. Recheck every 6 months or on landscape events (credible competitor, regulation, economic swing, tech shift, taste shift) — re-enter at step 4. What matters is customer perception of the change, not the change itself.
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.
- 3d ago First seen · 63 lines · 74 tokens per session scan A a391fd977a74
positioning is a skill published in the GitHub repository lucasheriques/shipmate (4 stars, last pushed 1mo ago), licensed MIT. It adds 74 tokens to every session and 1,644 once invoked, about $0.0004 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-roast
Get your startup plan roasted with data — Garry Tan style.
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-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.