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-schedule-recurring-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-schedule-recurring-event)<a href="https://agentmods.dev/skills/fakoli/fakoli-plugins/recipe-schedule-recurring-event"><img src="https://agentmods.dev/badge/skills/fakoli/fakoli-plugins/recipe-schedule-recurring-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-schedule-recurring-event"><img src="https://agentmods.dev/badge/skills/fakoli/fakoli-plugins/recipe-schedule-recurring-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.00016 | $0.00457 |
| Opus 5.5 | $0.00006 | $0.00183 |
| Sonnet 5.5 | $0.00003 | $0.00091 |
| Haiku 4.5 | $0.00002 | $0.00046 |
Grade A, and why
recipe-schedule-recurring-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 1mo 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
Schedule a Recurring Meeting
Create a recurring Google Calendar event with attendees.
When to Use
Use this workflow when the user wants to set up a repeating meeting — weekly standups, biweekly 1:1s, monthly reviews, etc.
Workflow
1. Gather details
Ask the user for:
- Title (e.g., "Weekly Standup")
- Day/time and timezone
- Duration
- Recurrence pattern (weekly, biweekly, monthly)
- Attendees (email addresses)
2. Build the recurrence rule
Common RRULE patterns:
- Weekly on Monday:
RRULE:FREQ=WEEKLY;BYDAY=MO - Biweekly on Tuesday:
RRULE:FREQ=WEEKLY;INTERVAL=2;BYDAY=TU - Monthly first Wednesday:
RRULE:FREQ=MONTHLY;BYDAY=1WE - Daily weekdays:
RRULE:FREQ=WEEKLY;BYDAY=MO,TU,WE,TH,FR
3. Create the event
gws calendar events insert \
--params '{"calendarId": "primary"}' \
--json '{"summary": "TITLE", "start": {"dateTime": "START", "timeZone": "TZ"}, "end": {"dateTime": "END", "timeZone": "TZ"}, "recurrence": ["RRULE"], "attendees": [{"email": "ATTENDEE"}]}' \
--dry-run
Confirm with the user, then execute.
4. Verify
gws calendar +agenda --days 14 --format table
Safety
- Always
--dry-runfirst — recurring events create many instances - Add
COUNT=Nto the RRULE to limit the number of occurrences
Tips
- Use
UNTIL=20261231T000000Zin the RRULE to set an end date - The first occurrence date is set by the
startfield, not the RRULE
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.
- 1mo ago First seen · 59 lines · 16 tokens per session scan A 436717d1e17e
recipe-schedule-recurring-event is a skill published in the GitHub repository fakoli/fakoli-plugins (4 stars, last pushed 1mo ago), licensed MIT. It adds 16 tokens to every session and 457 once invoked, about $0.0001 per session on Opus 5.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
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.
loop-orchestrator
Operate a fleet of durable agent loops under .loop/ — schedule which loop runs next, assign agents to roles (maker vs checker), enforce promotion gates from propose-only to write access, allocate budgets, detect stalled or dead loops, and roll up fleet status into one report. Use when asked to "run the loops"…
github-project-management
GitHub project management with issue tracking, project-board automation, and sprint planning. Use when triaging or organizing issues, automating a project board, planning a sprint, or running release/roadmap coordination on GitHub.
creator-productivity
Task management and workspace memory for creative work sessions. Manages a TASKS.md file for project tracking, a two-tier memory system (CREATOR.md + creator-memory/), and a daily sprint structure. Use when organizing creative projects, tracking content tasks, or starting a focused work session.
moai-gtd
Canonical GTD entry point for capture, clarification, organization, review, and engagement.
product-management-expert
Product management expertise for strategy, discovery, prioritization, roadmaps, PRDs, metrics, and stakeholder communication. Use when defining what to build, why, and how to measure success.