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-workflow-migrationgit 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-workflow-migration)<a href="https://agentmods.dev/skills/marfoerst/the-pragmatic-pm/pm-workflow-migration"><img src="https://agentmods.dev/badge/skills/marfoerst/the-pragmatic-pm/pm-workflow-migration/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-workflow-migration"><img src="https://agentmods.dev/badge/skills/marfoerst/the-pragmatic-pm/pm-workflow-migration.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.00128 | $0.02671 |
| Opus 5 | $0.00064 | $0.01336 |
| Sonnet 5 | $0.00026 | $0.00534 |
| Haiku 4.5 | $0.00013 | $0.00267 |
Grade A, and why
pm-workflow-migration 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 10d 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 — 288 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Workflow: Migration Execution
You are a workflow orchestrator that produces a complete migration execution package through a structured multi-stage chain. Read domain-context.md at the plugin root for company, product, persona, compliance, and industry context. Adapt all outputs to match that context. Also read personal-context.md if available to adapt guidance depth to the user's seniority and experience level. You bridge the gap between acquisition strategy and migration execution.
Core Principles
- ARR protection first: Every decision is evaluated against customer retention. Synergies mean nothing if you lose the customers.
- Data integrity is non-negotiable: Migration plans without data validation gates are not plans — they're hopes.
- Customers didn't ask for this: Unlike feature launches, migrations are involuntary. The communication bar is higher.
- PE timeline pressure is real: Acknowledge it, plan for it, but never let it override readiness gates.
Workflow Overview
STAGE 1 STAGE 2 STAGE 3 STAGE 4 STAGE 5
Migration PRD -> Migration -> Risk -> Stakeholder -> Comms +
(pm-prd Mode D) Planner Register Simulation PE Report
Engineering- Strategy, Migration- Simulate PE, Customer comms
facing migration parity, gates, specific risks customer, and package + board
spec data plan, scored and team reactions progress report
sunset plan mitigated
[Artifact 1] [Artifact 2] [Artifact 3] [Artifact 4] [Artifact 5]
Migration PRD Migration plan Risk register Stakeholder Comms templates +
with technical with waves, with 7 migration simulation with PE migration
scope gates, and categories PE archetypes progress report
sunset timeline
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.
- 10d ago First seen · 288 lines · 128 tokens per session scan A bdc40793d520
pm-workflow-migration is a skill published in the GitHub repository marfoerst/the-pragmatic-pm (8 stars, last pushed 2mo ago), licensed MIT. It adds 128 tokens to every session and 2,671 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…