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/dojogenesis/mcp/product-positioningnpx skills add DojoGenesis/mcp --skill product-positioninggit clone --depth 1 https://github.com/DojoGenesis/mcpWrote 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/dojogenesis/mcp/product-positioning)<a href="https://agentmods.dev/skills/dojogenesis/mcp/product-positioning"><img src="https://agentmods.dev/badge/skills/dojogenesis/mcp/product-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.1 | $0.00075 | $0.02302 |
| Opus 5 | $0.00037 | $0.01151 |
| Sonnet 5 | $0.00015 | $0.00460 |
| Haiku 4.5 | $0.00007 | $0.00230 |
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 6d 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 — 245 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Product Positioning Skill
Version: 1.1 Purpose: To guide the process of reframing a binary product decision into a strategic positioning opportunity by identifying the unique, contextual value of a product or feature.
I. The Philosophy: Beyond the Binary
The most common trap in product strategy is the binary choice: keep or kill, build or buy, deprecate or maintain. These choices are limiting because they assume the value of a product is fixed.
This skill operates on a different principle: value is contextual. A product's worth isn't inherent -- it's determined by the context in which it's used. A web app isn't "redundant" because a desktop app exists. It's uniquely good at discovery and onboarding -- things the desktop app can't do.
The core technique is the unlocking question: "What is this uniquely good at that the other thing isn't?" This question shatters the binary and opens up new strategic possibilities.
The core insight: The reframe is the prize, not the initial answer. The before/after shift in how you think about the product is more valuable than the decision itself.
II. When to Use This Skill
- When facing a decision about whether to keep or deprecate a feature or product
- When a product or feature seems redundant or is underperforming
- When planning a multi-surface product strategy (web, desktop, mobile)
- At the beginning of a strategic planning cycle
- Before using
/scoutto ensure the question is properly framed - When two products or features feel like they're competing rather than complementing
When NOT to use:
- When the product genuinely has no unique value (sometimes deprecation is the right call)
- When the decision is about timing, not positioning (use
/scoutinstead) - When you need to explore many options without a binary starting point (use
/scout; this skill is for binary reframes)
III. The Workflow
This is a 5-step workflow for reframing a product decision.
Step 1: Identify the Binary Trap
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.
- 6d ago First seen · 245 lines · 75 tokens per session scan A 176e6f62b608
product-positioning is a skill published in the GitHub repository DojoGenesis/mcp (0 stars, last pushed 1mo ago), licensed MIT. It adds 75 tokens to every session and 2,302 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
dd-code-generation
Use pup CLI for immediate Datadog operations or generate code for integration into applications.
redux-to-swr
Migrate React components from Redux + Saga to SWR hooks. Use when converting data fetching from Redux store (reducers, sagas, selectors, connect HOC) to SWR-based hooks in CockroachDB DB Console or cluster-ui.
mma-investigator
Expert system for investigating MMA (Multi-Metric Allocator) behavior on CockroachDB clusters. Helps oncall engineers diagnose load imbalances, understand rebalancing decisions, and identify why MMA did or didn't act.
migrate-state-management
Migrate Redux or React Context to the correct state option (React Query for server state, nuqs for URL/shareable state, Zustand for global client state). Use when refactoring away from Redux/Context, moving state to the right store, or when the user asks to migrate state management.
db-infra-mocks
Propose minimal seams and local substitutes so tests run without real RDBMS/Redis/Mongo infrastructure.
build-run
Build and run the project locally to reproduce compile/runtime issues in a safe, non-production way.