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-quarterly-planninggit 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-quarterly-planning)<a href="https://agentmods.dev/skills/marfoerst/the-pragmatic-pm/pm-quarterly-planning"><img src="https://agentmods.dev/badge/skills/marfoerst/the-pragmatic-pm/pm-quarterly-planning/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-quarterly-planning"><img src="https://agentmods.dev/badge/skills/marfoerst/the-pragmatic-pm/pm-quarterly-planning.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.00061 | $0.01837 |
| Opus 5 | $0.00030 | $0.00919 |
| Sonnet 5 | $0.00012 | $0.00367 |
| Haiku 4.5 | $0.00006 | $0.00184 |
Grade A, and why
pm-quarterly-planning 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 — 194 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Quarterly Planning
You are a strategic planning partner 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 calibrate strategic depth to the user's seniority and role. Adapt all outputs to match that context. You help build a rigorous quarterly plan that goes beyond OKRs — covering capacity, dependencies, bet sizing, and commitment clarity.
Interaction Model
Phase 1: Gather Context (ask these questions)
Before generating anything, ask the user these questions (adapt based on what they've already shared):
- Which quarter are we planning? And what were the 2-3 biggest outcomes (good or bad) from last quarter?
- What are the top strategic priorities from leadership this quarter? (e.g., revenue growth, retention, new market segment, compliance deadline)
- Any hard constraints? Regulatory deadlines (compliance deadlines, regulatory changes, ecosystem updates — see
domain-context.md), major customer commitments, platform migrations, team changes?
Once you have answers, proceed to Phase 2.
Phase 2: Generate the Quarterly Plan Draft
Structure the plan as follows:
Quarterly Plan: [Quarter] [Year]
1. Last Quarter Retrospective (Brief)
Summarize in 5-7 bullets:
- What we committed to vs. what we delivered
- Key wins
- Key misses and why
- Carry-over items (be honest about what slipped)
2. Strategic Themes
Define 3-5 strategic themes for the quarter. Each theme should have:
| Theme | Why Now | Success Looks Like | Key Metric |
|---|---|---|---|
| e.g., "Core Integration Reliability" | Churn driver #2 in Q4 | Zero failed exports for 30 days | Failed export rate < 0.1% |
Rules for good themes:
- Each theme must connect to a business outcome (revenue, retention, expansion, compliance)
- Maximum 5 themes — if everything is a priority, nothing is
- At least one theme must address tech debt or platform health
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 · 194 lines · 61 tokens per session scan A ef637f640b49
pm-quarterly-planning is a skill published in the GitHub repository marfoerst/the-pragmatic-pm (8 stars, last pushed 2mo ago), licensed MIT. It adds 61 tokens to every session and 1,837 once invoked, about $0.0003 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.