phuryn/pm-skills is a marketplace of reusable skills, commands, and plugins that guide AI assistants through product-management work such as discovery, strategy, planning, metrics, launches, and growth. It is for product managers and teams using Claude Code, Cowork, or compatible assistants. The catalogue entries are the project's own workflows and extensions.
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.
git clone --depth 1 https://github.com/phuryn/pm-skillsWrote 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/commands/phuryn/pm-skills/meeting-notes)<a href="https://agentmods.dev/commands/phuryn/pm-skills/meeting-notes"><img src="https://agentmods.dev/badge/commands/phuryn/pm-skills/meeting-notes.svg" alt="Measured on agentmods" 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.00018 | $0.00663 |
| Opus 5 | $0.00009 | $0.00331 |
| Sonnet 5 | $0.00004 | $0.00133 |
| Haiku 4.5 | $0.00002 | $0.00066 |
Grade A, and why
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 8d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- meeting-notes — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 90 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/meeting-notes -- Meeting Summary
Transform a raw meeting transcript or rough notes into clear, structured meeting minutes with decisions captured and action items assigned.
Invocation
/meeting-notes [paste transcript]
/meeting-notes [upload transcript file, audio summary, or notes]
Workflow
Step 1: Accept the Transcript
Accept in any format:
- Full transcript (from Otter, Fireflies, Google Meet, Zoom, etc.)
- Rough notes taken during the meeting
- Audio summary or meeting recap from a transcription tool
- Multiple inputs (e.g., transcript + the user's own notes)
If the input is sparse, work with what's available and flag gaps.
Step 2: Extract and Structure
Apply the summarize-meeting skill:
Parse the content to identify:
- Participants: Who was present (from introductions, speaker labels, or mentions)
- Topics discussed: Major agenda items or conversation threads
- Decisions made: Explicit agreements or conclusions reached
- Action items: Tasks assigned, with owner and deadline if mentioned
- Open questions: Unresolved items that need follow-up
- Key quotes: Important statements worth preserving verbatim
- Context: Meeting type, project, and background
Step 3: Generate Meeting Summary
## Meeting Summary
**Date**: [date if known]
**Participants**: [names/roles]
**Meeting type**: [standup, planning, review, 1:1, stakeholder, etc.]
**Topic**: [primary subject]
### Summary
[3-5 sentence overview of what was discussed and concluded]
### Key Decisions
1. **[Decision]** — [context and rationale]
2. ...
### Action Items
| # | Action | Owner | Deadline | Status |
|---|--------|-------|----------|--------|
### Discussion Highlights
**[Topic 1]**: [key points, different perspectives, conclusion]
**[Topic 2]**: [key points, different perspectives, conclusion]
### Open Questions
- [Question] — needs input from [person/team]
### Next Steps
- [What happens next]
- Next meeting: [if mentioned]
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.
- 8d ago First seen · 90 lines · 18 tokens per session scan A 46b84ae8e450
meeting-notes is a command published in the GitHub repository phuryn/pm-skills (26,066 stars, last pushed 2mo ago), licensed MIT. It adds 18 tokens to every session and 663 once invoked, about $0.0001 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-30.
Other commands, from other repositories
brief-me
Get briefed — loads your full memory, pulls live state from all connected tools, surfaces risks, staleness, upcoming milestones, and gives you a prioritized briefing so you're never starting blank.
value-prop-statements
Fan an existing positioning statement out into segment- and channel-specific value-prop copy variants, trace-checked against drift.
buyer-personas
Map the buying committee, then build alternatives-anchored messaging personas.
ideal-customer-profile
Build, enrich, or audit your ICP — trigger events, buyer map, JTBD, disqualifiers.
positioning-messaging
Build or audit positioning statements, messaging, and related output.
experiment-ideas
Generate several concrete, brain-grounded growth ideas — channel, message, rationale, cost-efficiency — ranked by effort vs. impact.