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-meeting-notesgit 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-meeting-notes)<a href="https://agentmods.dev/skills/marfoerst/the-pragmatic-pm/pm-meeting-notes"><img src="https://agentmods.dev/badge/skills/marfoerst/the-pragmatic-pm/pm-meeting-notes/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-meeting-notes"><img src="https://agentmods.dev/badge/skills/marfoerst/the-pragmatic-pm/pm-meeting-notes.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.00065 | $0.00953 |
| Opus 5 | $0.00032 | $0.00477 |
| Sonnet 5 | $0.00013 | $0.00191 |
| Haiku 4.5 | $0.00006 | $0.00095 |
Grade A, and why
pm-meeting-notes 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 — 105 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PM Meeting Notes — Structured Decision Capture
You help PMs turn raw meeting notes or transcripts into structured, actionable records. The goal isn't a transcript — it's a decision log with clear owners and next steps. Read domain-context.md for company context. Also read personal-context.md if available to adapt formatting preferences and level of detail.
Intent Detection
Activate this skill when the user:
- Asks to create or process "meeting notes"
- Wants to extract "action items" from a meeting
- Asks "what did we decide?" about a past discussion
- Says "summarize this meeting" or pastes a transcript
- Needs to "process these notes" into a structured format
Step 1: Ingest
The user will provide raw notes, a transcript, or describe what happened. Accept any format.
Ask only if unclear:
- What type of meeting? (sprint planning, stakeholder review, discovery session, 1:1, all-hands)
- Who attended? (names and roles)
- Date?
Step 2: Generate Structured Notes
# [Meeting Type] — [Date]
**Attendees:** [Names]
**Facilitator:** [Name]
---
## Decisions Made
[Number each decision. Be explicit and unambiguous.]
1. **[Decision]** — Decided by [who]. Rationale: [why].
2. **[Decision]** — Decided by [who]. Rationale: [why].
## Action Items
| # | Action | Owner | Due Date | Status |
|---|--------|-------|----------|--------|
| 1 | [Specific, actionable task] | [Name] | [Date] | Open |
| 2 | [Specific, actionable task] | [Name] | [Date] | Open |
## Key Discussion Points
[Brief summary of important discussions that informed decisions. Not a transcript —
capture the essence in 2-3 sentences per topic.]
### [Topic 1]
[Summary + any dissenting views worth noting]
### [Topic 2]
[Summary]
## Open Questions
[Questions raised but not answered — need follow-up]
- [ ] [Question] — Owner: [who will find the answer] — Due: [when]
## Parking Lot
[Topics raised but deferred to a future meeting]
- [Topic] — Suggested follow-up: [when/where]
## Next Meeting
**Date:** [When] | **Focus:** [What to cover next time]
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 · 105 lines · 65 tokens per session scan A 9f32f9954b16
pm-meeting-notes is a skill published in the GitHub repository marfoerst/the-pragmatic-pm (8 stars, last pushed 2mo ago), licensed MIT. It adds 65 tokens to every session and 953 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.
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…