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 surfmind-space/awesome-surfmind --skill calendar-prepgit clone --depth 1 https://github.com/surfmind-space/awesome-surfmindWrote 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/surfmind-space/awesome-surfmind/calendar-prep)<a href="https://agentmods.dev/skills/surfmind-space/awesome-surfmind/calendar-prep"><img src="https://agentmods.dev/badge/skills/surfmind-space/awesome-surfmind/calendar-prep/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/surfmind-space/awesome-surfmind/calendar-prep"><img src="https://agentmods.dev/badge/skills/surfmind-space/awesome-surfmind/calendar-prep.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.00066 | $0.00709 |
| Opus 5 | $0.00033 | $0.00354 |
| Sonnet 5 | $0.00013 | $0.00142 |
| Haiku 4.5 | $0.00007 | $0.00071 |
Grade A, and why
calendar-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 9d 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 — 58 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Calendar Prep
Turn the user's event page, calendar invite, email, or notes into everything they need to show up prepared. Work only from what is present; never invent attendees, times, locations, commitments, questions, or follow-up actions.
- Extract title, date/time, timezone, location or link, attendees, RSVP/status labels, purpose, agenda items, documents, and deadlines.
- Identify what the user should read, prepare, bring, decide, or ask before the event, but include only items directly supported by the source.
- Draft a short agenda from stated agenda items, purpose, or required decisions.
- Add follow-up reminders only for explicit deadlines, named required actions, or missing/ambiguous logistics or attendance statuses that the source itself exposes.
- If key details like date, time, or location are missing or ambiguous, flag them so the user can confirm before relying on the prep.
Return these sections, omitting any that do not apply: Event summary, Prep checklist, Agenda, Questions to ask, Follow-up reminders. Preserve names, numbers, links, dates, and attendee RSVP/status labels exactly as given. Do not infer availability or RSVP status: if someone is listed as maybe, declined, no response, optional, accepted, or similar, keep that label or omit attendance status rather than rewriting it as confirmed attendance. Treat Questions to ask as optional: include it only when the source states an uncertainty, missing detail, blocker, deadline, required decision, or explicit topic the user must ask about; do not convert ordinary agenda items into generic questions. Treat Follow-up reminders as optional and factual: do not add recap emails, stakeholder sign-offs, capacity checks, separate follow-ups, or decision prompts unless the source explicitly requires them. When unsure, omit the optional item rather than inventing useful-sounding prep. Respond in the same language as the user's request.
Example
Invite (selected text):
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.
- 9d ago First seen · 58 lines · 66 tokens per session scan A 87eedebf9fe3
calendar-prep is a skill published in the GitHub repository surfmind-space/awesome-surfmind (5 stars, last pushed 1mo ago), licensed MIT. It adds 66 tokens to every session and 709 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-31.
Other skills, from other repositories
cron
Use this skill only for scheduled or recurring tasks. Manage jobs with qwenpaw cron list/create/get/state/update/pause/resume/delete/run, and always pass --agent-id explicitly.
cron
A procedure for creating and managing tasks that run automatically at a future time or repeat on a schedule. It uses QwenPaw's scheduling commands and requires an agent identifier.
mailbox
A guide for performing email and mailbox tasks through the QwenPaw mailbox system. It covers supported personal email providers, credentials, configuration, and the required mailbox workflow.
channel_message
Use this skill to proactively send a one-way message to a user/session/channel, usually only when the user explicitly asks to send to a channel/session or when proactive notification is needed. First query sessions with qwenpaw chats list, then push with qwenpaw channels send.
cron-task-creator
Create, manage, and run scheduled automated tasks (cron jobs) in Clacky. Use this skill whenever the user wants to create a new automated task or cron job, set up recurring automation, schedule something to run daily/weekly/hourly, view all scheduled tasks, edit an existing task prompt or cron schedule, enable or…
meeting-summarizer
Summarize a completed meeting from its transcript. Produces a structured summary with key decisions, action items, and discussion highlights. Triggered automatically when a meeting ends.