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 cnfeat/top-pm-skills --skill meeting-notesgit clone --depth 1 https://github.com/cnfeat/top-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/skills/cnfeat/top-pm-skills/meeting-notes)<a href="https://agentmods.dev/skills/cnfeat/top-pm-skills/meeting-notes"><img src="https://agentmods.dev/badge/skills/cnfeat/top-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/skills/cnfeat/top-pm-skills/meeting-notes"><img src="https://agentmods.dev/badge/skills/cnfeat/top-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.00059 | $0.02247 |
| Opus 5 | $0.00030 | $0.01123 |
| Sonnet 5 | $0.00012 | $0.00449 |
| Haiku 4.5 | $0.00006 | $0.00225 |
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 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 — 285 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Meeting Notes Skill
This skill structures meeting notes to maximize value and ensure follow-through.
Required Inputs
Ask the user for these if not provided:
- Meeting title and date
- Attendees (names and roles)
- Raw notes or transcript (paste discussion notes, a transcript, or describe what was discussed)
- Meeting type (1:1 / sprint planning / product review / stakeholder sync / other) — determines which template to use
Standard Meeting Notes Template
Meeting Header
Meeting: [Meeting Title]
Date: [Date]
Attendees: [Names/Roles]
Note Taker: [Name]
Duration: [Actual duration]
Agenda
- Topic 1
- Topic 2
- Topic 3
(Check off items as discussed)
Decisions Made
Clear documentation of decisions:
Decision: [What was decided]
Context: [Why this decision]
Owner: [Who's responsible for executing]
Deadline: [When if applicable]
Use this format for each decision made.
Action Items
All action items should be:
- [Action item] - @Owner - Due: [Date]
- [Action item] - @Owner - Due: [Date]
Format:
- Clear, specific action
- Single owner (no "team" ownership)
- Concrete deadline
- Checkbox for tracking
Discussion Notes
Key points discussed organized by topic:
Topic 1: [Name]
- Key point or discussion highlight
- Important context or concern raised
- Any data or information shared
Topic 2: [Name]
- Key discussion points
- Decisions or conclusions reached
Open Questions / Follow-Up
Questions that couldn't be answered:
- Question: [What we need to know]
- Owner: [Who will find out]
- By When: [Deadline]
Next Steps
Clear summary of what happens next:
- [Immediate next action]
- [Follow-up meeting if needed]
- [Any broader process to start]
Best Practices
During the meeting:
- Focus on decisions and action items over dialogue
- Capture specific commitments, not general discussion
- Note dissenting opinions on important decisions
- Ask for clarity on vague commitments ("I'll look into it" → "I'll analyze the data and share findings by Friday")
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 · 285 lines · 59 tokens per session scan A be88dd8596e9
meeting-notes is a skill published in the GitHub repository cnfeat/top-pm-skills (48 stars, last pushed 3mo ago), licensed MIT. It adds 59 tokens to every session and 2,247 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-09-03.
Other skills, from other repositories
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.
magpie-security-issue-import-from-md
Open one or more tracking issues from a markdown file containing a batch of security findings. Each finding becomes one tracker landing in the Needs triage board column. The file itself is the full report — there is no inbound reporter to reply to and no PR to inspect.