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 leecyno1/boutique-skills --skill ai-meeting-notesgit clone --depth 1 https://github.com/leecyno1/boutique-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/leecyno1/boutique-skills/ai-meeting-notes)<a href="https://agentmods.dev/skills/leecyno1/boutique-skills/ai-meeting-notes"><img src="https://agentmods.dev/badge/skills/leecyno1/boutique-skills/ai-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/leecyno1/boutique-skills/ai-meeting-notes"><img src="https://agentmods.dev/badge/skills/leecyno1/boutique-skills/ai-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.00058 | $0.06516 |
| Opus 5 | $0.00029 | $0.03258 |
| Sonnet 5 | $0.00012 | $0.01303 |
| Haiku 4.5 | $0.00006 | $0.00652 |
Grade A, and why
ai-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 12d 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 ai-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 — 989 lines — stays where its author put it; the contents beside it link to each section on GitHub.
📋 AI Meeting Notes
Messy notes → Clear action items. Instantly.
Paste any meeting notes, transcript, or text. Get a clean summary with action items, owners, and deadlines.
No bot. No subscription. No setup.
⚠️ CRITICAL: RESPONSE FORMAT (READ FIRST)
When extracting meeting notes, you MUST respond with ALL of the following in ONE SINGLE MESSAGE:
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
📋 [MEETING TITLE] — [YYYY-MM-DD]
Duration: [X min] | Attendees: [Names]
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
SUMMARY
[2-3 sentence overview]
⚡ ACTION ITEMS ([X] of [Total])
1. [ ] @Owner: Task — Deadline
2. [ ] @Owner: Task — Deadline
3. [ ] @Owner: Task — Deadline
4. [ ] @Owner: Task — Deadline
5. [ ] @Owner: Task — Deadline
[Show up to 10, note "(+X more in file)" if more exist]
✅ KEY DECISIONS
• Decision 1
• Decision 2
📎 Saved: meeting-notes/YYYY-MM-DD_topic-name.md
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Add to your to-do list?
• "all" — Add all [X] items
• "1,2,4" — Add specific items
• "none" — Skip
MANDATORY RULES
| Rule | Requirement |
|---|---|
| ONE response | NEVER split into multiple messages. Display + file + to-do prompt in SINGLE response. |
| Filename format | MUST be YYYY-MM-DD_topic.md — Date FIRST, always. Example: 2026-02-02_anne-call.md |
| Action items numbered | ALWAYS show numbered list (1, 2, 3...) in chat for easy selection |
| To-do prompt | ALWAYS include the "Add to your to-do list?" prompt if action items exist |
| File attachment | ALWAYS attach/save the full .md file |
❌ NEVER DO THIS
- ❌ Send file first, then "Processing...", then "Done" (THREE messages)
- ❌ Filename without date:
anne-call-notes.md - ❌ Say "includes action items" without showing them
- ❌ Skip the to-do list prompt
- ❌ Ask user to request display separately
✅ ALWAYS DO THIS
- ✅ ONE message with everything
- ✅ Filename:
2026-02-02_anne-call.md(date first) - ✅ Show numbered action items in chat
- ✅ Include to-do prompt
- ✅ Attach full file
What ships with it
6 files 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.
- 12d ago First seen · 989 lines · 58 tokens per session scan A 21aca0db7f5e
ai-meeting-notes is a skill published in the GitHub repository leecyno1/boutique-skills (5 stars, last pushed today), licensed MIT. It adds 58 tokens to every session and 6,516 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to ai-meeting-notes, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
ai-meeting-notes
Messy notes → Clear action items. Instantly. Paste any meeting notes, transcript, or text. Get summaries, action items with owners and deadlines. Auto-saved, searchable, with integrated to-do tracking. No bot. No subscription. No setup.
scheduling
Set up recurring or scheduled work — anything the user wants run on a schedule, repeatedly, or at a future time ("every morning", "each weekday at 9am", "daily digest", "weekly report", "remind me", "run this on a cron"). Teaches how to author a durable Vexa Scheduler routine that survives restarts. Use this instead…
vexa-meetings
Work with the user's meetings through the Vexa MCP tools — send a bot to a call, follow the transcript while it runs, and write meetings into their notes (Obsidian, Notion, plain markdown) with speakers and action items. Use whenever the user mentions a meeting, a call, a transcript, meeting notes, or asks what was…
vexa-setup
Set up or fix the Vexa MCP connection for this plugin — where the API key comes from, hosted vs self-hosted URL, and how to check the connection. Use when the vexa server is missing, returns 401, or the user asks how to connect Vexa.
clean-messy-notes-to-action-items
Turn unstructured notes into action items with owners, deadlines, decisions, and unresolved follow-ups.
meeting-notes
Turn meeting transcripts or voice recordings into structured notes with action items, decisions, and owners. Use when the user shares a transcript, meeting recording, or asks to summarize a meeting. Triggers on: "meeting notes", "summarize this meeting", "action items from", "what was decided", "meeting summary"…