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 aniganti/pm-superpowers --skill strategygit clone --depth 1 https://github.com/aniganti/pm-superpowersWrote 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/aniganti/pm-superpowers/strategy)<a href="https://agentmods.dev/skills/aniganti/pm-superpowers/strategy"><img src="https://agentmods.dev/badge/skills/aniganti/pm-superpowers/strategy.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector pass
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.00080 | $0.03357 |
| Opus 5 | $0.00040 | $0.01679 |
| Sonnet 5 | $0.00016 | $0.00671 |
| Haiku 4.5 | $0.00008 | $0.00336 |
Grade A, and why
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 8d 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 — 312 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Product Strategy Framework
This is the main orchestrator skill for developing a product strategy. It implements a 6-step interactive framework grounded in Rumelt's strategy kernel (Why/What/How).
This skill is interactive. At each step, ask questions, wait for the PM's responses, then synthesize before moving on. Use "one round of questions at a time" pacing — do not overwhelm the PM with everything at once.
If the PM provides a path to an existing strategy document, read it first and use it as a starting point. Identify what is already covered and what gaps remain, then pick up the framework from the appropriate step.
Step 1: Understand the Market and Users
Start by building a deep understanding of the market, users, and competitive landscape.
Market Context
Ask the PM:
- What industry are you operating in?
- What stage is the market in? (emerging / growing / mature / declining)
- What is the regulatory environment? Are there compliance requirements or upcoming regulatory changes?
- What is the addressable market size (TAM, SAM, SOM)? How was it estimated?
Target Users
Ask the PM:
- Who are your target user segments?
- What personas have you defined? What are their key behaviors, motivations, and pain points?
- How do these segments differ from each other in terms of needs and willingness to pay?
Competitive Landscape
Ask the PM:
- Who are the known competitors — both direct and indirect?
- What are their value propositions and positioning?
- Where do they excel and where do they fall short?
Spawn the competitive-researcher agent with the market context, competitor names, and industry information gathered so far. This agent will gather competitive intelligence in parallel while you continue the conversation with the PM.
Existing Research
Ask the PM:
- What research has already been done? User interviews, surveys, support ticket analysis, usage data, market research reports?
- What are the key insights from that research?
- What gaps remain in your understanding?
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.
- 8d ago First seen · 312 lines · 80 tokens per session scan A e27f344f2168
strategy is a skill published in the GitHub repository aniganti/pm-superpowers (47 stars, last pushed 24d ago), licensed MIT. It adds 80 tokens to every session and 3,357 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-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…