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-ideasgit 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-ideas)<a href="https://agentmods.dev/skills/silverstein/minutes/minutes-ideas"><img src="https://agentmods.dev/badge/skills/silverstein/minutes/minutes-ideas/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-ideas"><img src="https://agentmods.dev/badge/skills/silverstein/minutes/minutes-ideas.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.00052 | $0.00344 |
| Opus 5 | $0.00026 | $0.00172 |
| Sonnet 5 | $0.00010 | $0.00069 |
| Haiku 4.5 | $0.00005 | $0.00034 |
Grade A, and why
minutes-ideas 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.
What it actually says
/minutes-ideas — Recent Voice Memos & Ideas
Surface voice memos and ideas captured from any device in the last 14 days. This is the recall layer for the cross-device ghost context pipeline.
How to run
- Search for recent voice memos using the
minutesCLI:
minutes list --content-type memo --limit 20
-
Require exit status 0 and use the JSON written to stdout. If the CLI is unavailable or fails, report the memo source unavailable; never scan the memo directory directly.
-
Present the memos as a clean list:
- Date, title, duration, device (if from iPhone)
- Ask: "Want to dig into any of these?"
-
If the user picks one, run
minutes get "<exact path>" --json, require exit status 0, and present only the returned transcript/summary. Never reopen the list path through the host filesystem.
Ghost Context
These memos were captured on the user's phone (or Mac) and automatically transcribed by the Minutes watcher. They may contain ideas, thoughts, observations, or reminders that the user recorded while away from their desk.
When the user asks "what was that idea I had while walking?" — search these memos first, then broaden to full meeting search if needed.
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.
- 11d ago First seen · 40 lines · 52 tokens per session scan A a68c7e1133e0
minutes-ideas is a skill published in the GitHub repository silverstein/minutes (1,471 stars, last pushed yesterday), licensed MIT. It adds 52 tokens to every session and 344 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-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…