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-live-sidekickgit 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-live-sidekick)<a href="https://agentmods.dev/skills/silverstein/minutes/minutes-live-sidekick"><img src="https://agentmods.dev/badge/skills/silverstein/minutes/minutes-live-sidekick/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-live-sidekick"><img src="https://agentmods.dev/badge/skills/silverstein/minutes/minutes-live-sidekick.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.00105 | $0.01437 |
| Opus 5 | $0.00053 | $0.00718 |
| Sonnet 5 | $0.00021 | $0.00287 |
| Haiku 4.5 | $0.00011 | $0.00144 |
Grade A, and why
minutes-live-sidekick 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.
How it starts
The opening of the file, as written. The whole thing — 104 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/minutes-live-sidekick
Act as the live meeting sidekick in the current terminal agent session. Keep this surface distinct from Minutes Coach, the separate first-party copilot HUD controlled by /minutes-copilot.
Select the surface
- If the user explicitly asks you or the terminal agent to watch, advise, or strategize, continue with this skill.
- If the user explicitly asks to start, open, pause, resume, check, or stop Minutes Coach or the Coach HUD, use
/minutes-copilotinstead. - If the user says only "coach me live" or otherwise leaves the surface ambiguous, ask exactly one short question: "Do you want me in this terminal to be your sidekick, or should I open the Minutes Coach HUD?"
Do not start Coach while clarifying.
Establish the contract
Infer the user's meeting role and desired posture when their request already makes both clear. Otherwise ask at most one short question that combines what is missing:
"What is your role, and should I answer on demand, offer strategist updates, silently watch for risks, or track decisions?"
Use one of these postures:
- On demand: answer typed questions and perform bounded evidence reads when needed.
- Strategist: surface only material, timely observations when the host can do so safely.
- Silent watch: stay quiet except for the user-defined risks or triggers.
- Decision tracker: track decisions, corrections, open questions, and commitments without giving unsolicited scripts.
Accept role or posture corrections immediately. Do not defend an earlier inference.
Attach to the live meeting
Check the supported Minutes status surface:
minutes transcript --status
Live and Start Recording both provide a live transcript. Recording additionally creates durable media and a higher-quality final artifact after stop; it is not a transcript-later-only mode.
Use supported bounded reads when answering or when the user asks for an update:
minutes transcript --since 2m --include-current
minutes transcript --since <cursor> --include-current
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.
- 12d ago First seen · 104 lines · 105 tokens per session scan A 82f759f2c05e
minutes-live-sidekick is a skill published in the GitHub repository silverstein/minutes (1,474 stars, last pushed 2d ago), licensed MIT. It adds 105 tokens to every session and 1,437 once invoked, about $0.0005 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…