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 cnfeat/top-pm-skills --skill platform-strategygit clone --depth 1 https://github.com/cnfeat/top-pm-skillsWrote 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/cnfeat/top-pm-skills/platform-strategy)<a href="https://agentmods.dev/skills/cnfeat/top-pm-skills/platform-strategy"><img src="https://agentmods.dev/badge/skills/cnfeat/top-pm-skills/platform-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/cnfeat/top-pm-skills/platform-strategy"><img src="https://agentmods.dev/badge/skills/cnfeat/top-pm-skills/platform-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.00042 | $0.00852 |
| Opus 5 | $0.00021 | $0.00426 |
| Sonnet 5 | $0.00008 | $0.00170 |
| Haiku 4.5 | $0.00004 | $0.00085 |
Grade A, and why
platform-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 11d 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 — 65 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Platform Strategy
Help the user design and execute platform business strategies using frameworks from 24 product leaders who have built and scaled platforms.
How to Help
When the user asks for help with platform strategy:
- Understand the platform type - Clarify whether they're building a marketplace, API platform, ecosystem, or developer platform
- Identify the network effects - Help them understand which sides of the platform create value for each other
- Assess the lifecycle stage - Determine if they're in the moat-building, opening, or closing phase
- Design for trust and governance - Help them think through the rules that will govern platform participants
Core Principles
Treat internal platforms as products
Camille Fournier: "Platform engineering is not just maintaining cloud infrastructure... platforms are products, ultimately. You should be thinking about how do I create coherent offerings that make this company more productive?" Internal platforms need dedicated product management and focus on user (developer) productivity, not just technical elegance.
Understand the four-stage platform lifecycle
Brian Balfour: "The four steps are essentially, one is I call a Step Zero. It's the conditions of the market have been met. Step One is about a moat, Step Two is about a platform opening, and Step Three is about the platform closing for control and monetization." Platforms follow a predictable lifecycle from market consensus to closing for monetization.
Reduce cognitive load through clear interfaces
Jeremy Henrickson: "The more you can bake into a clear platform, it reduces the decision-making complexity for everyone who's working on the domain part of the problem." A well-defined platform with clear interfaces simplifies product development by reducing the cognitive load on individual teams.
Find compounding dynamics
Alex Komoroske: "Anything that is shaped like an ecosystem that has some kind of network effect... you have to know what you're looking for and find the dynamics of a thing that if it worked would work at an accelerating rate." Platform success comes from identifying "gardening" opportunities - projects with inherent compounding loops that grow on their own.
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.
- 11d ago First seen · 65 lines · 42 tokens per session scan A 99544bf2a850
platform-strategy is a skill published in the GitHub repository cnfeat/top-pm-skills (48 stars, last pushed 2mo ago), licensed MIT. It adds 42 tokens to every session and 852 once invoked, about $0.0002 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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
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…