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 commands/spillwavesolutions/automating-mac-apps-plugin/meeting-startgit clone --depth 1 https://github.com/SpillwaveSolutions/automating-mac-apps-pluginWrote 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/commands/spillwavesolutions/automating-mac-apps-plugin/meeting-start)<a href="https://agentmods.dev/commands/spillwavesolutions/automating-mac-apps-plugin/meeting-start"><img src="https://agentmods.dev/badge/commands/spillwavesolutions/automating-mac-apps-plugin/meeting-start.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 | $0.00018 | $0.00196 |
| Opus 5 | $0.00009 | $0.00098 |
| Sonnet 5 | $0.00004 | $0.00039 |
| Haiku 4.5 | $0.00002 | $0.00020 |
Grade A, and why
meeting-start 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 4d 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
Meeting Start
Finds the in-progress meeting from Calendar and starts a Voice Memos recording for it.
Usage
/meeting-start
/meeting-start --now 2024-07-01T15:05
Behavior
- Looks up the current (or provided) time in Calendar to identify the meeting.
- Activates Voice Memos and starts recording, naming the memo after the meeting.
- Optionally notes attendance/state for follow-up (
meeting-end) and reminds that transcript/notes will be used downstream for action items.
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.
- 4d ago First seen · 28 lines · 18 tokens per session scan A efc01b8b7710
meeting-start is a command published in the GitHub repository SpillwaveSolutions/automating-mac-apps-plugin (40 stars, last pushed 13d ago), licensed MIT. It adds 18 tokens to every session and 196 once invoked, about $0.0001 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 commands, from other repositories
prompt
System instructions for writing effective prompts. Apply when generating commands, skills, agents, or any LLM instructions.
full
Run the full hope pipeline — intent, shape, target, freeze as needed — then execute.
save-chat
Save the current conversation to a document file.
codex-review
Run OpenAI Codex code review on current changes or a specific branch/commit.
extract
Analyze conversation history and extract reusable skills, commands, or agents.
raw-export
Export raw conversation data directly from JSONL session files.