aaif-create-event

aaif-create-event is a skill for Claude Code from aaif/community-events. It costs 92 tokens per session (2,006 once invoked), scanned A, original, MIT.

An event-creation guide for AAIF chapters and online series. It copies a sample event section into an event tracker, fills in details, and calculates task deadlines from the event date.

In plain words
What is it for?
Use it to add an event to an Event Tracker document and, with explicit approval, create its live Luma event page. Luma is a service for publishing event pages and handling registrations.
Why use it?
It prevents missed or inconsistent preparation deadlines when planning an event.

Skill for Claude Code

Written for Claude Code: argument-hint in frontmatter.

Part of the aaif-events plugin — 20 skills shipped together

Good fit Use it to add an event to an Event Tracker document and, with explicit approval, create its live Luma event page. Luma is a service for publishing event pages and handling registrations.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/aaif/community-events/aaif-create-event
Install

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.

Any agent
npx skills add aaif/community-events --skill aaif-create-event
Clone the repo
git clone --depth 1 https://github.com/aaif/community-events

Made for: Claude Code.

Or install aaif-events, the plugin that ships this one along with the rest of its 20 skills.

Wrote 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.

agentmods badge for aaif-create-event

README.md
[![agentmods](https://agentmods.dev/badge/skills/aaif/community-events/aaif-create-event.svg)](https://agentmods.dev/skills/aaif/community-events/aaif-create-event)
Your own site
<a href="https://agentmods.dev/skills/aaif/community-events/aaif-create-event"><img src="https://agentmods.dev/badge/skills/aaif/community-events/aaif-create-event.svg" alt="Measured on agentmods" height="20"></a>
Per session 92 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,006 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00092 $0.02006
Opus 5 $0.00046 $0.01003
Sonnet 5 $0.00018 $0.00401
Haiku 4.5 $0.00009 $0.00201

Measured 8d ago against content hash 79ae3c1554c9, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, from the pricing page.

Security

Grade A, and why

aaif-create-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 8d ago.

The scan reads SKILL.md. This mod also ships 4 executable files (scripts/create_event.py, scripts/luma_push.py, scripts/test_create_event.py, …), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

skills/aaif-create-event/SKILL.md · 137 lines

How it starts

The opening of the file, as written. The whole thing — 137 lines — stays where its author put it; the contents beside it link to each section on GitHub.

AAIF Create Event

Tooling rule — gws + Python only. Every read, edit, and write of a Drive file goes through the gws CLI, driven from Python. Prefer native Google formats: edit application/vnd.google-apps.* files with the Docs/Sheets/ Slides API. Drop to byte-level OOXML surgery on the .docx/.pptx/.xlsx zip 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 for unoconv and any desktop office suite. To see a file, render it through the API instead — a slide via aaif_events.slides_export.render_slide_png, a doc via gws drive files copy to a Google Doc → gws drive files export to PDF → trash the copy. Never round-trip a native Doc through .docx — it strips native features like Tabs.

Add a new event to a chapter/series Event Tracker.docx: clone the example event section, fill the detail block, and compute every phase task's DUE date backward from the event date (the template's exact cadence is preserved per task). Mode is implicit — a chapter clones the in-person task set, an online series the online set, because you download whichever tracker the folder holds.

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

  1. Locate the tracker. Chapters parent 1IQ1K7aVOKUUkxAcfLuNjdETEnmavvtjx, Online parent 1g2vHrqDHfh9wBkDJryJIl8wqXA4J-d4i. Find the named folder, then its Event Tracker.docx id (see aaif-event-status for the exact gws drive files list queries).

  2. Download it into a temp dir:

    WORK=$(mktemp -d)
    gws drive files get --params '{"fileId":"<DOC_ID>","alt":"media"}' --output $WORK/tracker.docx
    

    These 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.

Read the full file on GitHub · 137 lines

Files

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.

Changes

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.

  1. 8d ago First seen · 137 lines · 92 tokens per session scan A 79ae3c1554c9

Subscribe to this mod's changes

aaif-create-event is a skill published in the GitHub repository aaif/community-events (9 stars, last pushed yesterday), licensed MIT. It adds 92 tokens to every session and 2,006 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.