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-x1-send-meetinggit 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-x1-send-meeting)<a href="https://agentmods.dev/skills/silverstein/minutes/minutes-x1-send-meeting"><img src="https://agentmods.dev/badge/skills/silverstein/minutes/minutes-x1-send-meeting/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-x1-send-meeting"><img src="https://agentmods.dev/badge/skills/silverstein/minutes/minutes-x1-send-meeting.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.00094 | $0.02608 |
| Opus 5.5 | $0.00038 | $0.01043 |
| Sonnet 5.5 | $0.00019 | $0.00522 |
| Haiku 4.5 | $0.00009 | $0.00261 |
Grade A, and why
minutes-x1-send-meeting 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 10d 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 — 193 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/minutes-x1-send-meeting
Send one of the user's own meetings to their X1 household for review. Minutes supplies the meeting's outcomes. X1 decides who the sender is, which household it goes to, and what gets matched, and the user approves the send in X1. The meeting lands in the user's own review queue. Nothing reaches the household record until they confirm each item, and no professional sees it.
Required connections
This workflow needs both the local Minutes MCP and the official X1 MCP. Call
X1 get_user_capabilities first. If submit_my_meeting or
request_human_confirmation isn't mounted, stop: X1 hasn't turned meeting
sends on for this account yet. Don't substitute another X1 write tool, invent
an endpoint, or save the meeting somewhere else in X1.
Before using dueStatement or detail, inspect the mounted
submit_my_meeting input schema from MCP tools/list and check its
meeting.actionItems item properties. A mounted tool name alone does not
prove support for a field. If that schema is unavailable, an available X1
get_user_capabilities action proposal contract for submit_my_meeting
may supply the argument schema; capability discovery never grants approval.
If a needed field is absent or neither discovery path supplies its schema,
stop before requesting a send and ask: “Can you update or reconnect X1 so
it accepts this meeting's original timing or detail?” Do not silently drop
conditional timing or rewrite a task to work around an older backend.
Workflow
- Identify exactly one meeting the user attended. Use Minutes
search_meetingsorlist_meetingsif needed, thenget_meetingwithinclude_restricted: false. If it returns a restricted stub, stop: a restricted meeting is never sent. Confirm the meeting with the user by title and date when there is any doubt. Use only whatget_meetingreturns for this meeting. Don't pull decisions or commitments fromget_meeting_insightsor any other cross-meeting search, since those mix in other meetings.
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.
- 10d ago Changed · +44 lines 555bf35a2f03
- 18d ago First seen · 149 lines · 94 tokens per session scan A 777815de1ec1
minutes-x1-send-meeting is a skill published in the GitHub repository silverstein/minutes (1,557 stars, last pushed yesterday), licensed MIT. It adds 94 tokens to every session and 2,608 once invoked, about $0.0004 per session on Opus 5.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-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.
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…
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…