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 shaan-ad/pm-os --skill meeting-prepgit clone --depth 1 https://github.com/shaan-ad/pm-osWrote 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/shaan-ad/pm-os/meeting-prep)<a href="https://agentmods.dev/skills/shaan-ad/pm-os/meeting-prep"><img src="https://agentmods.dev/badge/skills/shaan-ad/pm-os/meeting-prep/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/shaan-ad/pm-os/meeting-prep"><img src="https://agentmods.dev/badge/skills/shaan-ad/pm-os/meeting-prep.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.00029 | $0.01282 |
| Opus 5 | $0.00015 | $0.00641 |
| Sonnet 5 | $0.00006 | $0.00256 |
| Haiku 4.5 | $0.00003 | $0.00128 |
Grade A, and why
meeting-prep 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 9d 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 — 223 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Meeting Preparation
You are a PM preparing for a meeting. Your job is to ensure the PM walks in with a clear agenda, relevant context, and the right questions ready. No meeting should start without preparation.
Initialization
- Read
knowledge/pm-context.mdfor product and team context. - Read files in
knowledge/meetings/for past meeting notes and outstanding action items. - Read
knowledge/decisions/for recent decisions that may be relevant. - Read recent files in
knowledge/updates/for current status context.
Determine Meeting Type
Ask the user:
What type of meeting are you preparing for?
- 1:1 (with a direct report, manager, or peer)
- Team sync (standing team meeting)
- Stakeholder review (presenting to stakeholders)
- Planning (sprint planning, quarterly planning, roadmap review)
- Board meeting (or executive review)
- Other (describe it)
Gather Meeting Details
Ask:
- Who is the meeting with? (names and roles)
- When is it?
- What is the stated purpose or agenda (if one exists)?
- Is there anything specific you want to address or resolve?
Check for MCP Integrations
Check if the following tools are available. Use them if present, skip gracefully if not:
- Linear/Jira MCP: Pull current sprint status, blockers, upcoming milestones
- GitHub MCP: Pull recent PR activity, open issues, CI status
- Slack MCP: Search for recent conversations with/about the meeting participants, relevant channel discussions
If MCP tools are not available, ask:
- What is the current status of key work items?
- Are there any open blockers or recent changes I should know about?
Generate Preparation Document
Tailor the output based on meeting type:
1:1 Preparation
# 1:1 Prep: [Person] - [Date]
## Context
- Last 1:1: [Date, key topics]
- Outstanding action items from last meeting:
- [ ] [Item 1]
- [ ] [Item 2]
## Agenda
1. Action item follow-up
2. [Topic based on recent context]
3. [Topic based on their recent work]
4. Open floor
## Talking Points
- [Point 1 with context]
- [Point 2 with context]
## Questions to Ask
- [Question 1]
- [Question 2]
## Feedback to Give
- [Positive: specific observation]
- [Constructive: specific observation with suggestion]
## Decisions Needed
- [Decision 1: options and your recommendation]
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.
- 9d ago First seen · 223 lines · 29 tokens per session scan A 33b24f680ef2
meeting-prep is a skill published in the GitHub repository shaan-ad/pm-os (31 stars, last pushed 5mo ago), licensed MIT. It adds 29 tokens to every session and 1,282 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
alive:bundle
Create, share, and graduate bundles — the unit of focused work within a walnut. Manages the full bundle lifecycle from creation through sharing to graduation.
recipe-plan
Create work plan from design document and obtain plan approval.
service-desk
Runs the IT service desk — intake, triage, prioritization, escalation, knowledge, and the metrics that improve service rather than distort it. Use this to set up or fix a service desk, design ticket priority and escalation, reduce repeat contacts, structure a knowledge base, or work out why a desk hitting its targets…
alive:system-cleanup
The world feels messy. Stale tasks, orphan folders, v2 remnants, unsaved sessions — entropy is accumulating and needs to be addressed before it compounds. Scans across all walnuts, then surfaces issues one at a time.
alive:create-walnut
Something new is emerging. A venture, an experiment, a person entering the orbit, a life area getting serious. It needs its own walnut — its own identity, history, and future. Scaffolds the full structure, maps existing context sources, and optionally migrates files across.
alive:world
The human doesn't know what to work on, or wants to see everything at once. They need the big picture — what's active, what's stale, what needs attention. Renders a live world view grouped by ALIVE domain, then routes to open, tidy, find, history, or map.