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 commands/pytexas/meetup/update-meetupgit clone --depth 1 https://github.com/pytexas/meetupWhat 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.00014 | $0.00237 |
| Opus 5 | $0.00007 | $0.00118 |
| Sonnet 5 | $0.00003 | $0.00047 |
| Haiku 4.5 | $0.00001 | $0.00024 |
Grade A, and why
update-meetup 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 2d 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
Fetch the meetup.com event page at the following URL and extract the speaker and talk information:
$ARGUMENTS
Use WebFetch to retrieve the page content. Extract the following details:
- Event date (the date of the meetup)
- Talk title
- Speaker name
- Talk description (full description)
- Speaker bio (if available on the page)
- Speaker headshot URL (if available on the page)
After extracting this information, present it to the user for confirmation before proceeding.
Once confirmed, use the "meetup-update" skill to execute the full monthly update workflow:
- Archive the current meetup from the homepage into a past meetup post
- Add the new speaker to the authors file
- Update the homepage with the new meetup details
- Check for this month's Mailchimp newsletter draft; create it and draft the meetup copy if missing
If any required information is missing from the meetup.com page (e.g., speaker bio, headshot), ask the user to provide it before continuing with the update.
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.
- 2d ago First seen · 26 lines · 14 tokens per session scan A 4a8320693ab2
update-meetup is a command published in the GitHub repository pytexas/meetup (2 stars, last pushed 8d ago), licensed MIT. It adds 14 tokens to every session and 237 once invoked, about $0.0001 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 commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
constitution
Create or update the project constitution from interactive or provided principle inputs.