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 agentmods add skills/sonichi/sutando/meeting-prepnpx skills add sonichi/sutando --skill meeting-prepgit clone --depth 1 https://github.com/sonichi/sutandoWrote 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/sonichi/sutando/meeting-prep)<a href="https://agentmods.dev/skills/sonichi/sutando/meeting-prep"><img src="https://agentmods.dev/badge/skills/sonichi/sutando/meeting-prep.svg" alt="Measured on agentmods" 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.00035 | $0.00656 |
| Opus 5 | $0.00017 | $0.00328 |
| Sonnet 5 | $0.00007 | $0.00131 |
| Haiku 4.5 | $0.00003 | $0.00066 |
Grade A, and why
meeting-prep 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 6d 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 — 81 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Meeting Prep
Prepare a briefing for an upcoming meeting — attendee info, recent context, and talking points.
Usage: /meeting-prep [meeting name or time]
ARGUMENTS: $ARGUMENTS
How it works
- Find the meeting. If ARGUMENTS specifies a meeting name or time, find it. Otherwise, find the next meeting starting within 60 minutes.
$CLAUDE_CONFIG_DIR/skills/google-calendar/scripts/google-calendar.py events list \
--time-min NOW --time-max NOW_PLUS_60MIN
-
Extract attendees. From the calendar event, get the list of attendee emails.
-
Look up each attendee. For each attendee (skip the owner):
a. Contacts — search by email:
python3 $CLAUDE_CONFIG_DIR/skills/macos-tools/scripts/contacts.py search "[email protected]"b. Recent emails — search Gmail for recent threads with this person:
gws gmail users messages list --params 'q=from:[email protected] OR to:[email protected] newer_than:14d'Read the top 2-3 threads to extract context.
c. Web presence — if the person is external or unfamiliar, do a quick web search for their name + company to understand their role.
-
Build the brief. Generate a concise prep document:
Meeting: [title]
Time: [start] - [end]
Location: [link or room]
Attendees:
- [Name] ([role/company]) — [1-line context from recent emails]
- ...
Recent context:
- [Key thread 1 summary]
- [Key thread 2 summary]
Suggested talking points:
- [Based on recent threads and meeting title]
- ...
Action items to follow up on:
- [Any commitments from prior meetings/emails]
- Deliver. Write to
results/meeting-prep-{timestamp}.txtso the voice agent can speak it. Also write tonotes/meeting-prep-{date}-{title-slug}.mdfor reference.
Auto-scheduling
The proactive loop should check for meetings starting in the next 30-45 minutes. If one is found and no prep exists yet, run this skill automatically. Add this check to the proactive loop:
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.
- 6d ago First seen · 81 lines · 35 tokens per session scan A d28eb8560aed
meeting-prep is a skill published in the GitHub repository sonichi/sutando (392 stars, last pushed today), licensed MIT. It adds 35 tokens to every session and 656 once invoked, about $0.0002 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
gmail
Manage Gmail email — drafting, sending, organizing, filters, vacation replies, and inbox analysis.
schedule
Reminders, automations, and recurring page, dashboard, or status monitoring (cron, RRULE, or fire-at).
inbox-management
Ongoing Gmail inbox management via scheduled runs. Archives known noise, flags urgent items, drafts replies in-thread (never auto-sends), and catches stale follow-ups. Empty polls spend no model tokens. Starts in flag-only mode.
inbox-cleanup
Run a high-recall, multi-pass email inbox cleanup. Pattern-based subject queries catch 25x more archivable email than sender scans alone. Includes urgency triage, classification signals, and post-cleanup filter setup.
outlook
Manage Outlook email — drafting, sending, organizing, rules, vacation replies, and inbox analysis.
notifications
Send notifications through the unified notification router.