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 Avyayalaya/agent-prime --skill product-strategygit clone --depth 1 https://github.com/Avyayalaya/agent-primeWrote 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/avyayalaya/agent-prime/product-strategy)<a href="https://agentmods.dev/skills/avyayalaya/agent-prime/product-strategy"><img src="https://agentmods.dev/badge/skills/avyayalaya/agent-prime/product-strategy/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/avyayalaya/agent-prime/product-strategy"><img src="https://agentmods.dev/badge/skills/avyayalaya/agent-prime/product-strategy.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.00071 | $0.18904 |
| Opus 5 | $0.00036 | $0.09452 |
| Sonnet 5 | $0.00014 | $0.03781 |
| Haiku 4.5 | $0.00007 | $0.01890 |
Grade A, and why
product-strategy 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- product-strategy — 91% identical, 98 lines differ
How it starts
The opening of the file, as written. The whole thing — 1,118 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Purpose
Produce an elite-tier strategic product roadmap that articulates a falsifiable vision, sizes and sequences strategic bets with explicit confidence levels, surfaces tensions between competing priorities, names what you are NOT doing and what that costs, allocates resources against capacity constraints, and sets quarterly gates with kill criteria. The output is a Strategy Document — not a feature backlog, not a Gantt chart, but a decision architecture that tells a team what to build, in what order, why, and what to stop doing.
When to Use / When NOT to Use
Use this skill when:
- Building or revising a product roadmap for a quarter, half, or year
- Articulating product vision and translating it to executable strategy
- Running annual or quarterly planning exercises
- Making portfolio allocation decisions across multiple investment areas
- A leadership review requires a strategy document with clear bets and sequencing rationale
- You need to explicitly communicate what you are NOT doing and why
Do NOT use this skill when:
- You need competitive intelligence to inform the strategy (use Competitive Market Analysis skill first — its output feeds this skill)
- You need to write a specification for a specific feature (use Specification Writing skill — this skill's output feeds that one)
- You need to define metrics for measuring success of shipped features (use Metric Design & Experimentation skill)
- You need to understand a problem before deciding what to build (use Problem Framing skill — that comes upstream)
- You need a project plan with task-level assignments and sprint breakdowns (this is strategy, not project management)
Anti-inputs (what this skill does NOT handle):
- Feature specifications or PRDs (downstream: Specification Writing skill)
- Sprint planning or task decomposition (execution layer, not strategy layer)
- Competitive analysis (upstream: Competitive Market Analysis skill)
- User research synthesis (upstream: Discovery Research skill)
- OKR writing (adjacent but distinct — this skill produces the strategy that OKRs measure)
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 1,118 lines · 71 tokens per session scan A f77674e9fb16
product-strategy is a skill published in the GitHub repository Avyayalaya/agent-prime (8 stars, last pushed 3mo ago), licensed MIT. It adds 71 tokens to every session and 18,904 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
product-strategy
Use when building product strategy, roadmaps, or strategic plans — vision articulation, strategic bet definition, roadmap sequencing, resource allocation, portfolio planning, or quarterly/annual planning. Encodes bet-sizing, option-value sequencing, strategic tension surfacing, and explicit deprioritization. Produces…
strategy-generate
Create, modify, and optimize quantitative trading strategies, then backtest and evaluate them.
bottleneck-hunter
Supply-chain bottleneck arbitrage. Given a super-trend (AI infra, energy transition, defense, semiconductor reshoring, space economy), decompose its physical supply chain down to Layer 2/3 choke points (optics, lasers, InP/SOI substrates, IC substrates, probe cards, specialty fiberglass...) and surface under-the-radar…
execution-model
Trade execution modeling (backtest only) — slippage formulas (linear / square-root impact), VWAP/TWAP execution logic, market-impact cost estimation, and execution-assumption configuration.
ml-strategy
Machine-learning predictive strategy based on sklearn walk-forward training, feature engineering, and signal generation. Suitable for any OHLCV data.
event-driven
Event-driven strategy based on sentiment-scored signals from news, announcements, and macro events. The LLM acts as the NLP engine, and event data follows a CSV schema.