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 fakoli/fakoli-plugins --skill recipe-batch-invite-to-eventgit clone --depth 1 https://github.com/fakoli/fakoli-pluginsWrote 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/fakoli/fakoli-plugins/recipe-batch-invite-to-event)<a href="https://agentmods.dev/skills/fakoli/fakoli-plugins/recipe-batch-invite-to-event"><img src="https://agentmods.dev/badge/skills/fakoli/fakoli-plugins/recipe-batch-invite-to-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/fakoli/fakoli-plugins/recipe-batch-invite-to-event"><img src="https://agentmods.dev/badge/skills/fakoli/fakoli-plugins/recipe-batch-invite-to-event.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.00023 | $0.00415 |
| Opus 5 | $0.00012 | $0.00208 |
| Sonnet 5 | $0.00005 | $0.00083 |
| Haiku 4.5 | $0.00002 | $0.00042 |
Grade A, and why
recipe-batch-invite-to-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 7d 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
Add Multiple Attendees to a Calendar Event
Add a list of attendees to an existing Google Calendar event and send notifications.
When to Use
Use this workflow when the user needs to add multiple people to an existing event, or bulk-invite a team to a meeting.
Workflow
1. Find the event
Show the user's upcoming events so they can identify the right one:
gws calendar +agenda --format table
2. Get current event details
Fetch the event to see existing attendees (you'll need to preserve them):
gws calendar events get --params '{"calendarId": "primary", "eventId": "EVENT_ID"}' \
--fields "summary,attendees"
3. Add new attendees
Merge the existing attendee list with the new ones. Use --dry-run first:
gws calendar events patch \
--params '{"calendarId": "primary", "eventId": "EVENT_ID", "sendUpdates": "all"}' \
--json '{"attendees": [EXISTING_PLUS_NEW_ATTENDEES]}' \
--dry-run
Confirm with the user, then execute without --dry-run.
4. Verify
gws calendar events get --params '{"calendarId": "primary", "eventId": "EVENT_ID"}' \
--fields "summary,attendees"
Safety
- Always preview with
--dry-runbefore patching - Use
"sendUpdates": "all"so attendees get notified - Preserve existing attendees — the
attendeesfield is a full replacement, not an append
Tips
- Ask the user for email addresses as a comma-separated list
- The
attendeesarray replaces the entire list — always include existing attendees
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.
- 7d ago First seen · 63 lines · 23 tokens per session scan A a4e967975774
recipe-batch-invite-to-event is a skill published in the GitHub repository fakoli/fakoli-plugins (4 stars, last pushed 5d ago), licensed MIT. It adds 23 tokens to every session and 415 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-09-03.
Other skills, from other repositories
issue-triage
Use when the user wants to triage GitHub issues - decide whether an issue is still relevant, reproducible, closeable, a duplicate, or what concretely needs doing. Selects and prioritizes first (never dumps all issues at once), then deep-triages the chosen issues via parallel subagents, recommends actions for the owner…
requirements-verbatim
Capture a user requirement, decision, approval, or constraint word-for-word into an append-only dated log so it survives context compaction and can never be trimmed, softened, or reinterpreted. Use whenever the user states or approves a requirement, gives a GO, sets a constraint, or makes any decision that later work…
work-planning
Design the complete work hierarchy for a Paperclip company — Goals, Projects, and Tasks as a unified top-down planning workflow. Produces .planning.json for deterministic generation of goals/, projects/, and tasks/ directories. Use when creating a new company's work plan, reorganizing work structure, or linking goals…
project
A single starting point for setting up an AI-assisted project in Claude Cowork. It asks questions about the work, reviews available add-ons, and creates project instructions, custom agents, and connected workflows.
hr-operations
A skill for designing remote-work and team-operation policies. It covers flexible work, asynchronous communication, collaboration tools, productivity tracking, and employee experience.
hr-performance-review
A skill for designing and running employee performance reviews. It covers MBO, OKRs, KPIs, 360-degree feedback, review guides, and feedback conversations; OKRs set goals and measurable results, while KPIs track ongoing performance.