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 skills/pytexas/meetup/meetup-updatenpx skills add pytexas/meetup --skill meetup-updategit clone --depth 1 https://github.com/pytexas/meetupWrote 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/pytexas/meetup/meetup-update)<a href="https://agentmods.dev/skills/pytexas/meetup/meetup-update"><img src="https://agentmods.dev/badge/skills/pytexas/meetup/meetup-update.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.00196 | $0.03673 |
| Opus 5 | $0.00098 | $0.01836 |
| Sonnet 5 | $0.00039 | $0.00735 |
| Haiku 4.5 | $0.00020 | $0.00367 |
Grade A, and why
Monthly Meetup Update 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 3d 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 — 269 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Monthly Meetup Update
This skill runs the full monthly setup for the next PyTexas Meetup. It mirrors the recurring Todoist task "Schedule Monthly Meetup" (every 2nd Wednesday, in the PyTexas project), which is the checklist of record.
Overview
The Todoist subtasks and how this skill handles each:
- Update Meetup Website - automated here: archive the held meetup, add the speaker to authors, update the homepage, open a PR
- Create Canva Card - attempted via the Canva MCP; flagged with the design's edit link if editing fails
- Send Social Media Assets to Kassandra - handled by posting to the Discord marketing channel webhook
- Create Discord Event - automated via
scripts/create_discord_event.py - Create Network Event on Meetup - automated via
scripts/create_meetup_event.py - Create Event on Non-network meetups (MKE) - manual, flagged at the end
Beyond the Todoist list, the skill also drafts the month's Mailchimp newsletter and creates the meetup-night materials in Drive: the month folder, the run of show doc, and the attendance and questions forms.
Speaker data always comes from the Google MCP first (Drive for the CFP sheet, Gmail for the booked date). If Todoist is connected, re-read the subtasks of "Schedule Monthly Meetup" at the start in case the checklist has changed, and follow the live list over the one above.
Template Policy
Every artifact this skill produces is template-driven. Use the reference template verbatim and fill only the marked slots; never rewrite, paraphrase, or improvise the template prose. The outreach email, run of show, attendance form, Canva card, and Kassandra email each have a reference file listed at the bottom. If Mason changes an artifact's wording, update its template file so the next run produces the new exact version.
Input Data
Always pull from the Google MCP first. The other input options are fallbacks for when Drive is unavailable or the user hands over data directly.
Primary Source: CFP Responses Spreadsheet (Google Drive)
What ships with it
17 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.
- references/announcements.md 3.2 KB
- references/canva-cards.md 3.2 KB
- references/discord-event.md 3.1 KB
- references/discord-webhook.md 2.8 KB
- references/drive-artifacts.md 4.8 KB
- references/file-formats.md 3.0 KB
- references/local-meetups.md 1.4 KB
- references/meetup-event.md 4.8 KB
- references/newsletter.md 4.8 KB
- references/outreach-email.md 1.6 KB
- references/run-of-show.md 5.2 KB
- references/temporal-dispatch.md 2.6 KB
- scripts/build_announcements.py 4.2 KB runs code
- scripts/create_discord_event.py 5.2 KB runs code
- scripts/create_meetup_event.py 8.4 KB runs code
- scripts/scrape_local_meetups.py 4.7 KB runs code
- scripts/send_discord_announcement.py 2.6 KB runs code
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.
- 3d ago First seen · 269 lines · 196 tokens per session scan A 5f19f616938a
Monthly Meetup Update is a skill published in the GitHub repository pytexas/meetup (2 stars, last pushed 9d ago), licensed MIT. It adds 196 tokens to every session and 3,673 once invoked, about $0.0010 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
pingpong
Spontaneous local leisure meetups via a shared agent board: publish, discover and match offers, then negotiate place & time agent-to-agent. ALWAYS use this skill when the user spontaneously wants to do something or says: "publish an offer", "I want to play table tennis / X", "fancy a ...", "who's free for ...", "find…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.