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 assimovt/productskills --skill product-positioninggit clone --depth 1 https://github.com/assimovt/productskillsWrote 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/assimovt/productskills/product-positioning)<a href="https://agentmods.dev/skills/assimovt/productskills/product-positioning"><img src="https://agentmods.dev/badge/skills/assimovt/productskills/product-positioning/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/assimovt/productskills/product-positioning"><img src="https://agentmods.dev/badge/skills/assimovt/productskills/product-positioning.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.00684 |
| Opus 5 | $0.00026 | $0.00342 |
| Sonnet 5 | $0.00010 | $0.00137 |
| Haiku 4.5 | $0.00005 | $0.00068 |
Grade A, and why
product-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 12d 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 — 64 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Position products by starting from what customers would do without you — not from your features or aspirations. April Dunford's Obviously Awesome framework works because it's grounded in reality: what alternatives exist, what you do differently, and who cares most about that difference.
The Five Steps (In Order)
These steps are sequential. Do NOT skip ahead or rearrange.
1. Competitive Alternatives
What would your best customers do if you didn't exist? List real alternatives:
- Direct competitors
- Indirect solutions (spreadsheets, hiring someone, different tools)
- Do nothing
Be honest. If "do nothing" is the primary alternative, that tells you a lot about urgency.
2. Unique Attributes
What do you have that the alternatives don't? List concrete, verifiable capabilities — not marketing spin.
- "Real-time collaboration on specs" (verifiable)
- NOT "best-in-class experience" (unverifiable)
3. Value
What do those unique attributes ENABLE for the customer? Translate features into outcomes.
- Attribute: "Real-time cursors and inline comments on any document"
- Value: "Get feedback from your team in minutes instead of waiting for a meeting"
4. Best-Fit Customers
Who cares MOST about the value you deliver? Define them tightly:
- "Remote teams of 5-15 who collaborate daily but drown in Slack threads and lost Google Docs"
- NOT "product managers" (too broad)
Best-fit customers have: the problem acutely, tried alternatives, have budget/authority, and get the most value from your unique attributes.
5. Market Category
What market do you position in so that your value is obvious? This is the LAST decision, not the first.
Options:
- Existing category: "We're a [known category] that [key differentiator]." Works when the category is well-understood and your differentiator is strong.
- Subcategory: "We're [modifier] + [existing category]." Works when you serve a specific segment better. E.g., "async-first collaboration tool."
- New category: Create a new name. Only works if you have the budget and patience to educate the market. Almost always the wrong choice for startups.
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.
- 12d ago First seen · 64 lines · 52 tokens per session scan A eebb5252d91c
product-positioning is a skill published in the GitHub repository assimovt/productskills (68 stars, last pushed 6mo ago), licensed MIT. It adds 52 tokens to every session and 684 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
prd-taskmaster
Zero-config goal-to-tasks engine (the Atlas engine). Takes any goal (software, pentest, business, learning), runs adaptive discovery via brainstorming, generates a validated spec, parses into TaskMaster tasks, and hands off to execution. Use when user says "PRD", "product requirements", "I want to build", invokes…
handoff
Phase 3 of the prd-taskmaster pipeline: smart mode selection and user handoff. Detects installed capabilities (superpowers, ralph-loop, task-master-ai, playwright, research providers), recommends ONE execution mode (A/B/C) with reasoned justification, appends the task-execution workflow to CLAUDE.md, surfaces a…
generate
Phase 2 of the prd-taskmaster pipeline: spec generation and task parsing. Loads a template (comprehensive|minimal), fills it with DISCOVER-phase constraints and answers, validates the spec (placeholdersfound, grade thresholds), parses the PRD into tasks via task-master, runs TaskMaster's native complexity analysis…
discover
Phase 1 of the prd-taskmaster pipeline: brainstorm-driven discovery. Delegates to superpowers:brainstorming in Interactive Mode (one adaptive question at a time), or self-brainstorms in Autonomous Mode when no user is present. Intercepts before the brainstorming chain hands off to writing-plans — this skill owns the…
execute-fleet
Phase execution skill for licensed Atlas Fleet runs. Use when HANDOFF has selected Atlas Fleet and the project should be executed across isolated launcher worktrees with inbox-based result collection, verified CDD cards, sequential integration merges, and one final PR.
customise-workflow
Customise the prd-taskmaster plugin workflow via curated brainstorm questions. The AI asks, the user answers in plain English, and the skill writes their preferences to .atlas-ai/config/atlas.json. Future runs of prd-taskmaster read that file and apply user preferences to phase gates, validation strictness, default…