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/pm-skills-arsenal --skill product-strategygit clone --depth 1 https://github.com/Avyayalaya/pm-skills-arsenalWrote 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/pm-skills-arsenal/product-strategy)<a href="https://agentmods.dev/skills/avyayalaya/pm-skills-arsenal/product-strategy"><img src="https://agentmods.dev/badge/skills/avyayalaya/pm-skills-arsenal/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/pm-skills-arsenal/product-strategy"><img src="https://agentmods.dev/badge/skills/avyayalaya/pm-skills-arsenal/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.20618 |
| Opus 5 | $0.00036 | $0.10309 |
| Sonnet 5 | $0.00014 | $0.04124 |
| Haiku 4.5 | $0.00007 | $0.02062 |
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.
This is a copy
91% identical to product-strategy — 98 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 1,214 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,214 lines · 71 tokens per session scan A e306b8d7b458
product-strategy is a skill published in the GitHub repository Avyayalaya/pm-skills-arsenal (6 stars, last pushed 3mo ago), licensed MIT. It adds 71 tokens to every session and 20,618 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. It is 91% identical to product-strategy, differing in 98 lines, and is treated as a copy.
Other skills, from other repositories
html-ppt-knowledge-arch-blueprint
OpenDesign's incident retro: the daemon-restart data bug, the root cause, the fix, and the systemic follow-ups. Built as a decision-grade product management deck for engineering, SRE, leadership.
html-ppt-graphify-dark-graph
OpenDesign's feature business case for the plugin marketplace: the user pain, options, tradeoffs, and the measure of success. Built as a decision-grade product management deck for PM, eng, design, leadership.
strategic-thinking-and-alignment
Develops the daily habits and communication practices that separate strategic leaders from operational ones. Covers carving out time for strategic thinking, communicating strategic changes effectively, building organisational alignment, challenging the status quo, and fostering competitive innovation without…
technical-roadmap-planning
Gathers inputs, defines initiatives, prioritises with an impact/effort matrix, sequences dependencies, and produces a roadmap table. Invoked when the user asks to plan a technical roadmap, prioritise engineering initiatives, or create a quarter/half-year engineering plan.
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…
replit-deck
For product and technical management work: turn PRDs, roadmaps, RFCs, architecture reviews, and retros into decision documents. Built around the core query "pm-feature-business-case-deck", with product strategy lead judgment, buyer-ready proof, and this outcome: approve the feature, architecture, roadmap, or incident…