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-update-eventgit 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-update-event)<a href="https://agentmods.dev/skills/aaif/community-events/aaif-update-event"><img src="https://agentmods.dev/badge/skills/aaif/community-events/aaif-update-event/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-update-event"><img src="https://agentmods.dev/badge/skills/aaif/community-events/aaif-update-event.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00108 | $0.01731 |
| Opus 5 | $0.00054 | $0.00865 |
| Sonnet 5 | $0.00022 | $0.00346 |
| Haiku 4.5 | $0.00011 | $0.00173 |
Grade A, and why
aaif-update-event 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 — 120 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AAIF Update Event
Tooling rule —
gws+ Python only. Every read, edit, and write of a Drive file goes through thegwsCLI, driven from Python. Prefer native Google formats: editapplication/vnd.google-apps.*files with the Docs/Sheets/ Slides API. Drop to byte-level OOXML surgery on the.docx/.pptx/.xlsxzip parts (embedded fonts and untouched parts survive) only when the file genuinely is a stored Office file. Never use LibreOffice /soffice— not to edit, not to convert, and not to render a "just checking it locally" preview: it substitutes local system fonts for the brand fonts and drops OOXML it doesn't understand, so its output and its renders both misrepresent the real file. Same forunoconvand any desktop office suite. To see a file, render it through the API instead — a slide viaaaif_events.slides_export.render_slide_png, a doc viagws drive files copyto a Google Doc →gws drive files exportto PDF → trash the copy. Never round-trip a native Doc through.docx— it strips native features like Tabs.
Change-driven editor for one event in a chapter/series Event Tracker.docx. State the
change; the script edits the right detail fields. If you move the date, every phase task
DUE date is recomputed (clock-time day-of tasks are left alone). It reports which
downstream assets (banner, Luma cover, posts, slides) are now stale so you can re-run
those skills — it does not regenerate them.
You (the agent) drive Google Drive via the gws CLI; the Python script only does the
deterministic docx edit on a local file. Prereq: gws installed and authenticated
(gws-cli-access).
Steps
-
Locate + download the tracker (Chapters parent
1IQ1K7aVOKUUkxAcfLuNjdETEnmavvtjx, Online parent1g2vHrqDHfh9wBkDJryJIl8wqXA4J-d4i; seeaaif-event-statusfor thegws drive files listqueries):WORK=$(mktemp -d) gws drive files get --params '{"fileId":"<DOC_ID>","alt":"media"}' --output $WORK/tracker.docxThese downloads hold organizer, speaker, and venue details — keep them in the temp dir and never commit them (or any
tracker.docx/luma.md/banner.png/new.*) to the repo.
What ships with it
4 files 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.
- 9d ago First seen · 120 lines · 108 tokens per session scan A 6c48975cbba4
aaif-update-event is a skill published in the GitHub repository aaif/community-events (9 stars, last pushed 2d ago), licensed MIT. It adds 108 tokens to every session and 1,731 once invoked, about $0.0005 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
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.