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-executive-updategit 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-executive-update)<a href="https://agentmods.dev/skills/marfoerst/the-pragmatic-pm/pm-executive-update"><img src="https://agentmods.dev/badge/skills/marfoerst/the-pragmatic-pm/pm-executive-update/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-executive-update"><img src="https://agentmods.dev/badge/skills/marfoerst/the-pragmatic-pm/pm-executive-update.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.00076 | $0.01314 |
| Opus 5 | $0.00038 | $0.00657 |
| Sonnet 5 | $0.00015 | $0.00263 |
| Haiku 4.5 | $0.00008 | $0.00131 |
Grade A, and why
pm-executive-update 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 — 141 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PM Executive Update — SCQA-Structured Leadership Communication
You help product leaders write executive updates that are concise, insightful, and action-oriented. No one wants to read a list of features shipped — executives want to know what moved, why it matters, and what needs their attention. Read domain-context.md for company and industry context. Also read personal-context.md if available to adapt tone, depth, and reporting cadence to the user's role.
Intent Detection
Activate this skill when the user:
- Asks for an "executive update" or "status report"
- Needs to write an "investor update" or "board update"
- Says "what should I report?" or "monthly business review"
- Wants to create a "weekly update" for leadership
- Asks to "summarize progress" for stakeholders or executives
Framework: SCQA
Every update follows the Situation-Complication-Question-Answer structure:
- Situation: Where we are right now (context, current state)
- Complication: What changed or what's at risk (the tension)
- Question: What needs to be decided or understood (the "so what?")
- Answer: What we're doing about it (the resolution)
Step 1: Gather Context
Ask the user these questions (skip what you can infer):
- Audience: Who is this for? (Board, CEO, investors, leadership team, cross-functional stakeholders)
- Time period: What period does this cover? (week, month, quarter)
- Key developments: What happened? What shipped? What moved? What didn't?
- Metrics movement: Which numbers went up/down/sideways? (need actuals vs targets)
- Blockers or risks: What needs escalation or decision-making?
- Asks: Do you need anything from the audience? (resources, decisions, alignment)
Step 2: Structure the Update
For Weekly Updates (keep under 1 page)
## Product Update — Week of [Date]
### TL;DR
[2-3 sentences: biggest win, biggest risk, any asks]
### What Moved
- [Outcome-focused bullets — "X shipped, enabling Y" not just "shipped X"]
### Metrics Snapshot
| Metric | Target | Actual | Trend |
|--------|--------|--------|-------|
| [Leading indicator] | X | Y | ↑↓→ |
| [Lagging indicator] | X | Y | ↑↓→ |
### Risks & Blockers
- [What's at risk, what decision is needed, by when]
### Next Week Focus
- [Top 3 priorities]
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 · 141 lines · 76 tokens per session scan A 89b6ff4ae5ac
pm-executive-update is a skill published in the GitHub repository marfoerst/the-pragmatic-pm (8 stars, last pushed 2mo ago), licensed MIT. It adds 76 tokens to every session and 1,314 once invoked, about $0.0004 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…