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/unixcrh/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/unixcrh/phuryn-pm-skills/meeting-notes)<a href="https://agentmods.dev/commands/unixcrh/phuryn-pm-skills/meeting-notes"><img src="https://agentmods.dev/badge/commands/unixcrh/phuryn-pm-skills/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/commands/unixcrh/phuryn-pm-skills/meeting-notes"><img src="https://agentmods.dev/badge/commands/unixcrh/phuryn-pm-skills/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.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 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.
This is a copy
100% identical to meeting-notes — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
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.
- 11d ago First seen · 90 lines · 18 tokens per session scan A 46b84ae8e450
meeting-notes is a command published in the GitHub repository unixcrh/phuryn-pm-skills (2 stars, last pushed 6mo 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. It is 100% identical to meeting-notes, differing in 0 lines, and is treated as a copy.
Other commands, from other repositories
template
Manage issue templates for streamlined issue creation.
sync-linear
Sync current work with Linear ticket status.
add-note
Add an internal or external note to a ConnectWise PSA ticket.
fest-show
Show festival progression (in-progress tasks, roadmap, and dependency view).
dispatcher
Pick the next-best repo to work on across the portfolio — rank free repos, recommend one, claim its lease atomically, and route to the entry command.
workpm
A project-management workflow for coordinating multiple AI workers through five stages. It includes task assignment, shared activity logs, worker replacement, and final checks.