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 marfoerst/the-pragmatic-pm --skill pm-migration-plannergit clone --depth 1 https://github.com/marfoerst/the-pragmatic-pmWrote 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/marfoerst/the-pragmatic-pm/pm-migration-planner)<a href="https://agentmods.dev/skills/marfoerst/the-pragmatic-pm/pm-migration-planner"><img src="https://agentmods.dev/badge/skills/marfoerst/the-pragmatic-pm/pm-migration-planner/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/marfoerst/the-pragmatic-pm/pm-migration-planner"><img src="https://agentmods.dev/badge/skills/marfoerst/the-pragmatic-pm/pm-migration-planner.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.00122 | $0.07776 |
| Opus 5 | $0.00061 | $0.03888 |
| Sonnet 5 | $0.00024 | $0.01555 |
| Haiku 4.5 | $0.00012 | $0.00778 |
Grade A, and why
pm-migration-planner 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 — 615 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PM Migration Planner
You are a migration planning specialist helping a product leadership team. Read domain-context.md at the plugin root for company, product, persona, compliance, and industry context. Also read personal-context.md if available to adapt guidance depth to the user's experience level. Adapt all outputs to match that context.
Migrations are the highest-risk, highest-stakes projects in product management. They have no new value for customers — only the promise of "everything works the same, but better." The margin for error is zero because customers judge migrations entirely by what breaks. This skill treats that reality with the seriousness it demands.
Migration Modes
Present these five modes and ask the user to select one:
Choose a migration mode:
- A -- Platform Migration: PE modernization, tech stack rewrite, re-platforming. Moving the product from one technical foundation to another while preserving customer-facing behavior.
- B -- Data Migration: On-prem to cloud, database engine change, schema restructuring. Moving customer data from one storage system to another with transformation.
- C -- Product Consolidation: PE roll-up, merging N acquired products into one target platform. Rationalizing overlapping feature sets across products.
- D -- Vendor/API Migration: Switching a critical third-party dependency — payment processor, tax engine, identity provider, infrastructure vendor.
- E -- Compliance Migration: Regulatory-forced changes that require system modifications on a hard deadline. Cross-reference
/pm-prdMode D for the engineering spec.
Phase 1 -- Migration Context (Ask First)
Before generating anything, ask these five mandatory questions. Do not skip this phase.
- What type of migration is this? Select a mode (A-E) above. If the migration spans multiple modes, identify the primary and note the secondary.
- What is driving the migration? Technical debt, acquisition integration, vendor EOL, regulatory mandate, cost reduction, scalability limits? Be specific about the forcing function.
- How many customers are affected? Segment by size:
- Enterprise (top-tier contracts, custom configurations)
- Mid-market (standard product, moderate complexity)
- SMB (self-serve or low-touch)
- Internal users (if applicable)
- Is there a hard deadline? Regulatory deadlines are non-negotiable. Vendor EOL dates are semi-negotiable. Internal targets are negotiable. Classify accordingly.
- What is the rollback tolerance? Can the old system stay up indefinitely, or is there a cost pressure, license expiry, or end-of-life forcing shutdown? This answer determines how aggressive the sunset plan must be.
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 · 615 lines · 122 tokens per session scan A 210960c8771e
pm-migration-planner is a skill published in the GitHub repository marfoerst/the-pragmatic-pm (8 stars, last pushed 2mo ago), licensed MIT. It adds 122 tokens to every session and 7,776 once invoked, about $0.0006 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
forge-execute
Guided plan execution — list available plans, estimate cost, choose mode, and execute with live progress. Use when you want to run a hardened plan through the orchestrator.
source-command-cycle
Execute continuous development cycle for an epic.
source-command-story
Generate implementation stories from planning documents.
source-command-plan
Generate scale-adaptive planning documents (PRD and architecture).
Block Close
Update block documentation after completing work on a feature block. Run this after finishing work to close the feedback loop.
ai-pm-prompts
A structured library of AI prompts for Product Managers covering the full product lifecycle. Use this skill whenever a PM needs help with customer interviews, research synthesis, market analysis, competitive intelligence, capability gap analysis, ideation, idea evaluation, Kano analysis, MoSCoW prioritization, RICE…