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 aaif/community-events --skill aaif-attendee-remindergit clone --depth 1 https://github.com/aaif/community-eventsWrote 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/aaif/community-events/aaif-attendee-reminder)<a href="https://agentmods.dev/skills/aaif/community-events/aaif-attendee-reminder"><img src="https://agentmods.dev/badge/skills/aaif/community-events/aaif-attendee-reminder/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/aaif/community-events/aaif-attendee-reminder"><img src="https://agentmods.dev/badge/skills/aaif/community-events/aaif-attendee-reminder.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.00054 | $0.00475 |
| Opus 5 | $0.00027 | $0.00237 |
| Sonnet 5 | $0.00011 | $0.00095 |
| Haiku 4.5 | $0.00005 | $0.00047 |
Grade A, and why
aaif-attendee-reminder 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.
What it actually says
AAIF Attendee Reminder
Sent to RSVPs ~1 week out and the morning of. Short, logistics-first (~70 words). Lead with date, time, and exact venue / entry. One line on the speaker. End by asking them to update their RSVP if plans change so the seat can be released.
House voice: warm, concrete, builder-to-builder. Signal, not numbers. Never include emails, phone numbers, door codes, or attendee names that are not already public in any post, slide, or message.
Standard footer (always include). After the closing update-your-RSVP sentence, append one quiet line with the two standing AAIF attendee links (defaults on every reminder), e.g. "Reminder: our Code of Conduct (https://events.linuxfoundation.org/about/code-of-conduct) and Privacy Policy (https://www.linuxfoundation.org/legal/privacy-policy) apply." This sits outside the ~70-word body count.
Input (from the event tracker)
- Event :
[EVENT TITLE]When:[DATE], doors [TIME] - Venue :
[VENUE / ENTRY NOTES]Speaker:[SPEAKER + TOPIC]
Example (tested — match this format and voice)
Agentic AI Night:
You're set for Agentic AI Night this Wednesday, June 24 — doors 17:30 in SoMa, San Francisco (exact address and door code land in your inbox the morning of). Maya Chen opens with tool calling at 10M requests a day, then three quick community demos. If your plans change, please update your RSVP so we can pass your seat to the waitlist. See you there.
Reminder: our Code of Conduct (https://events.linuxfoundation.org/about/code-of-conduct) and Privacy Policy (https://www.linuxfoundation.org/legal/privacy-policy) apply.
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 First seen · 38 lines · 54 tokens per session scan A 342561720611
aaif-attendee-reminder is a skill published in the GitHub repository aaif/community-events (9 stars, last pushed today), licensed MIT. It adds 54 tokens to every session and 475 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…