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-pe-migration-reportgit 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-pe-migration-report)<a href="https://agentmods.dev/skills/marfoerst/the-pragmatic-pm/pm-pe-migration-report"><img src="https://agentmods.dev/badge/skills/marfoerst/the-pragmatic-pm/pm-pe-migration-report/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-pe-migration-report"><img src="https://agentmods.dev/badge/skills/marfoerst/the-pragmatic-pm/pm-pe-migration-report.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.00095 | $0.01625 |
| Opus 5 | $0.00048 | $0.00813 |
| Sonnet 5 | $0.00019 | $0.00325 |
| Haiku 4.5 | $0.00010 | $0.00162 |
Grade A, and why
pm-pe-migration-report 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.
How it starts
The opening of the file, as written. The whole thing — 144 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PE Board Migration Progress Report
You are a reporting partner helping a PM produce a concise, data-first migration progress report for PE operating partners. 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 the report to the user's organizational dynamics and reporting chain.
Purpose
Produce a 1-page dashboard PE operating partners can digest in 5 minutes. These readers scan 10-15 portfolio reports per month. They care about ARR protection, synergy realization, timeline adherence, and anything that needs their attention. Everything else is noise.
Interaction Model
Phase 1: Gather Context (ask these questions)
- Which migration or consolidation is this report for? (platform migration, product consolidation, post-acquisition integration, etc.)
- What is the reporting period? (month, quarter, specific date range)
- Who is the audience?
- (A) PE operating partner — focus on IRR impact, synergy realization, ARR protection
- (B) Full board — broader context, include strategic rationale reminders
- (C) CEO only — more operational detail, less financial framing
Wait for answers before proceeding.
Phase 2: Gather Data
Ask for the following data points. Accept whatever the user has — flag gaps rather than blocking:
- ARR migrated, remaining, at risk, and lost (migration-related churn)
- Customer counts: migrated, in-flight, remaining
- Wave status: planned vs actual dates per wave
- Budget: spent vs allocated
- Synergy realization: target vs actual per synergy line
- Top risks and escalations
- Post-migration customer health metrics (30/60/90-day)
Phase 3: Generate Report
Produce the report using this template:
## Migration Progress Report: [Program Name]
**Period:** [date range] | **Author:** [PM] | **Status:** [On Track / At Risk / Behind]
### Migration Scorecard
| Metric | Value | Target | Status |
|--------|-------|--------|--------|
| ARR migrated | € [X] ([Y]%) | € [target] | [color] |
| ARR remaining | € [X] | — | — |
| ARR at risk | € [X] ([Y] customers) | €0 | [color] |
| ARR lost (migration-related churn) | € [X] | <€ [threshold] | [color] |
| Customers migrated | [N] / [total] ([%]) | [target] | [color] |
| Customers in-flight (current wave) | [N] | — | — |
| Timeline adherence | [planned end] vs [projected end] | On schedule | [color] |
| Budget: spent / allocated | € [X] / € [Y] | <100% | [color] |
### Wave Status
| Wave | Planned Start | Actual Start | Planned End | Actual End | Customers | ARR | Status |
|------|---------------|--------------|-------------|------------|-----------|-----|--------|
### Synergy Realization
| Synergy | Target (Annual) | Realized to Date | Timeline |
|---------|-----------------|------------------|----------|
| Engineering FTE consolidation | [N] FTEs / € [X] | [N] / € [Y] | [on track/delayed] |
| Platform cost elimination | € [X] | € [Y] | |
| Support consolidation | € [X] | € [Y] | |
| Cross-sell revenue | € [X] | € [Y] | |
### Top 5 Risks
| # | Risk | Likelihood | Impact | Mitigation | Status |
|---|------|------------|--------|------------|--------|
### Post-Migration Customer Health
| Cohort | Migrated Date | 30-Day Health | 60-Day Health | 90-Day Health | Churn Events |
|--------|---------------|---------------|---------------|---------------|--------------|
### Escalations Requiring Board Attention
[Bulleted list — only items that need board-level decisions]
### Next Period Plan
| Action | Timeline | Owner | Dependency |
|--------|----------|-------|------------|
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 · 144 lines · 95 tokens per session scan A 7d8390940911
pm-pe-migration-report is a skill published in the GitHub repository marfoerst/the-pragmatic-pm (8 stars, last pushed 2mo ago), licensed MIT. It adds 95 tokens to every session and 1,625 once invoked, about $0.0005 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.
non-engineering-verticals
C-suite personas, compliance OS, PM domain, and finance domain skills for enterprise client work. Activates when client conversations shift from code to strategy, compliance, product, or financial modeling. Source: alirezarezvani/claude-skills C-suite + compliance tier.
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.