Minutes is an open-source, local-first meeting recorder that transcribes meetings, calls, and voice memos on the device and stores the results as Markdown files. It is for people who want their meeting records available to Claude Code, Codex, Cursor, and other MCP clients without uploading them. The catalogue add-ons extend agent workflows for querying and using those local meeting files.
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 silverstein/minutes --skill minutes-recapgit clone --depth 1 https://github.com/silverstein/minutesWrote 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/silverstein/minutes/minutes-recap)<a href="https://agentmods.dev/skills/silverstein/minutes/minutes-recap"><img src="https://agentmods.dev/badge/skills/silverstein/minutes/minutes-recap/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/silverstein/minutes/minutes-recap"><img src="https://agentmods.dev/badge/skills/silverstein/minutes/minutes-recap.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00078 | $0.00834 |
| Opus 5 | $0.00039 | $0.00417 |
| Sonnet 5 | $0.00016 | $0.00167 |
| Haiku 4.5 | $0.00008 | $0.00083 |
Grade A, and why
minutes-recap 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.
How it starts
The opening of the file, as written. The whole thing — 67 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill Path
Before running helper scripts or opening bundled references, set:
export MINUTES_SKILLS_ROOT="$(git rev-parse --show-toplevel)/.agents/skills/minutes"
export MINUTES_SKILL_ROOT="$MINUTES_SKILLS_ROOT/minutes-recap"
/minutes-recap
Synthesize today's policy-authorized normal meetings and voice memos into a single daily brief. Restricted history is excluded from this agent workflow by default and must never be treated as absent evidence.
How to generate the recap
-
Find today's recordings from the bounded live list:
minutes list --limit 50Require exit status 0, parse the JSON written to stdout, and select entries whose
dateis today. A date string is not a search query. -
Read each selected recording with
minutes get "<exact path>" --json. Require exit status 0 and use only the returned content. Never reopen list paths through the host filesystem. -
Synthesize into a daily brief — use the template in
templates/daily-recap.mdas a starting point, adapting sections based on what actually exists in the day's recordings. -
Present the recap directly in the conversation — don't save it to a file unless asked.
What makes a good recap
- Cross-reference across meetings: if pricing came up in two different calls, note that
- Surface conflicts: if Meeting A decided X but Meeting B discussed doing Y, flag it
- Prioritize action items: these are the things the user needs to act on
- Include voice memos: ideas captured on the go are easy to forget — surface them
- If there are no meetings or memos today, say so clearly rather than making something up
Interactive conflict detection
When you find conflicts between meetings (e.g., different decisions on the same topic, contradictory action items, or shifted priorities), don't just note them — ask the user about them.
Use AskUserQuestion: "I found a conflict between your meetings today: [Meeting A] decided [X], but [Meeting B] discussed doing [Y]. Which one is current?"
What ships with it
2 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.
- 11d ago First seen · 67 lines · 78 tokens per session scan A 2854706b8c3e
minutes-recap is a skill published in the GitHub repository silverstein/minutes (1,473 stars, last pushed today), licensed MIT. It adds 78 tokens to every session and 834 once invoked, about $0.0004 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
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…
steno
Make the agent aware of the user's Steno meeting notes and able to pull them in on request. Steno (https://github.com/stenolabs/stenoai) records, transcribes, and summarizes meetings entirely on-device, storing each as a Markdown summary plus a transcript. This skill locates that store cross-platform (macOS, Windows…
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…
meeting_notes
Structure raw meeting notes into actionable minutes with follow-ups.
focus-and-priority-management
Delivers daily scheduling habits, meeting hygiene, attention management, and boundary-setting techniques for leaders whose calendars have become their strategy by default. Use when urgent tasks crowd out important ones, when meeting load exceeds productive work time, when a leader cannot recall their last hour of…
granola-to-steno
Sync Granola meeting notes into Steno's file-based store. Reads recent meetings from the Granola MCP (titles, dates, participants, AI summaries, verbatim transcripts) and regenerates Steno's output/summary.md and transcripts/transcript.txt files in a target folder (e.g. an iCloud Drive directory). The operation is…