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 agentmods add skills/arezous/pm-pilot/meeting-notesnpx skills add arezous/pm-pilot --skill meeting-notesgit clone --depth 1 https://github.com/arezous/pm-pilotWrote 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/arezous/pm-pilot/meeting-notes)<a href="https://agentmods.dev/skills/arezous/pm-pilot/meeting-notes"><img src="https://agentmods.dev/badge/skills/arezous/pm-pilot/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 | $0.00025 | $0.02213 |
| Opus 5 | $0.00013 | $0.01107 |
| Sonnet 5 | $0.00005 | $0.00443 |
| Haiku 4.5 | $0.00003 | $0.00221 |
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 4d 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 — 275 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an expert at extracting structured, actionable information from raw meeting content. You help product managers turn messy transcripts and notes into clear decisions, action items, and insights.
Read template/meeting-notes.md as the base structure for all outputs. The skill adds smart layers on top (timeline conflict detection, experiment flagging, cross-referencing PRDs) but the template defines the core sections.
Source and destination
- Raw transcripts and recordings live in:
data/meetings/ - Processed notes go to:
output/meetings/ - When finalized, output moves to
context/meetings/
The skill accepts input two ways: files in data/meetings/, or pasted directly into the conversation. If data/meetings/ has unprocessed files, offer to process them.
Accepted inputs
- Files in
data/meetings/(transcripts, voice memos, raw notes) - Pasted directly: Zoom/Otter/Grain/Google Meet transcripts, bullet-point notes, voice memo dictation, Slack threads, email chains
- Verbal brain dump ("let me tell you what happened")
Input length guidance
| Transcript length | Approach |
|---|---|
| < 30 min (under ~5,000 words) | Process normally in one pass |
| 30-60 min (~5,000-10,000 words) | Process normally, may compress detail |
| 60-90 min (~10,000-15,000 words) | Split into logical segments by topic or agenda item |
| 90+ min (15,000+ words) | Ask user to provide in chunks, or identify the most important segment first |
For very long transcripts, offer three approaches: full processing (compress less important sections), key segments only (user picks what matters), or chunked processing (paste in 2-3 parts).
Step 0: Gather context
Before processing, check what's relevant:
- Read
context/company.mdandcontext/product.mdfor grounding. - Check
context/meetings/(if it exists) for previous meetings on the same topic. - Check
context/prd/andoutput/prd/for related PRDs or feature context. - Check
context/personas.mdif it's a customer interview.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 4d ago First seen · 275 lines · 25 tokens per session scan A f5bb0995e05f
meeting-notes is a skill published in the GitHub repository arezous/pm-pilot (20 stars, last pushed 4mo ago), licensed MIT. It adds 25 tokens to every session and 2,213 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 skills, from other repositories
auth-web-cloudbase
CloudBase Web Authentication Quick Guide for frontend integration after auth-tool has already been checked. Provides concise and practical Web authentication solutions with multiple login methods and complete user management.
browse-and-evaluate
Use when exploring the ai-agent-skills catalog to find, compare, and evaluate skills before installing. Always use --fields to limit output size and --dry-run before committing to an install.
render-airdrop-carousel
Assemble a viral iOS "AirDrop" notification-carousel video ad (≈6–8s, 9:16) from a brand line plus 6–16 real product photos — a native AirDrop share-sheet card ("Brand would like to share a · Decline / Accept") springs up and its preview window CYCLES through the products, landing on a range/lineup payoff with an…
render-3d-product-showcase
Assemble a premium 3D product-showcase ad from a config — four beat clips (an orbiting hero rotation, a macro push-in, a physics reveal, a typographic close) normalized to the brand-color canvas, hard-concatenated in order, closed on a deterministic Playwright brand end card, and mixed under one instrumental bed at…
loop-engineering
Shared loop-engineering reference for COG skills - the agent loop, deterministic verifiers, termination conditions, in-loop context management, and named patterns. Invoke when designing or debugging a skill that iterates (search-verify-retry, scan-until-dry, fetch-retry-gate).
telnyx-messaging-hosted-curl
Set up hosted SMS numbers, toll-free verification, and RCS messaging. Use when migrating numbers or enabling rich messaging features. This skill provides REST API (curl) examples.