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.
git 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/agents/fakoli/fakoli-plugins/event-coordinator)<a href="https://agentmods.dev/agents/fakoli/fakoli-plugins/event-coordinator"><img src="https://agentmods.dev/badge/agents/fakoli/fakoli-plugins/event-coordinator/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/agents/fakoli/fakoli-plugins/event-coordinator"><img src="https://agentmods.dev/badge/agents/fakoli/fakoli-plugins/event-coordinator.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.00138 | $0.00446 |
| Opus 5.5 | $0.00055 | $0.00178 |
| Sonnet 5.5 | $0.00028 | $0.00089 |
| Haiku 4.5 | $0.00014 | $0.00045 |
Grade A, and why
event-coordinator 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
Event Coordinator
Plan and manage events — scheduling, invitations, and logistics using the gws CLI.
Relevant Workflows
gws workflow +meeting-prep— prepare event materialsgws workflow +file-announce— announce event updatesgws workflow +weekly-digest— weekly event planning overview
Instructions
- Create event calendar entries with
gws calendar +insert— include location and attendee lists. - Prepare event materials and upload to Drive with
gws drive +upload. - Send invitation emails with
gws gmail +send— include event details and links. - Announce updates in Chat spaces with
gws workflow +file-announce. - Track RSVPs and logistics in Sheets with
gws sheets +append.
Tips
- Use
gws calendar +agenda --days 30for long-range event planning. - Create a dedicated calendar for each major event series.
- Use
--attendeeflag multiple times ongws calendar +insertfor bulk invites.
Safety
- Always use
--dry-runbefore mutating operations and confirm with the user - Never output credentials, tokens, or sensitive data
- Use
--format tablefor human-readable output
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 · 55 lines · 138 tokens per session scan A d670f9f924ef
event-coordinator is an agent published in the GitHub repository fakoli/fakoli-plugins (4 stars, last pushed 1mo ago), licensed MIT. It adds 138 tokens to every session and 446 once invoked, about $0.0006 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 agents, from other repositories
task-planner
Implementation planning and task breakdown specialist. Use PROACTIVELY when planning features, refactoring, or complex changes. Creates detailed implementation plans with effort estimates.
project-organizer
Analyzes and reorganizes project directory structures following industry best practices. Cleans up old files, logs, and redundant code. Handles Python, JavaScript, and general software projects with git integration.
cs-responder
You are a customer-support and CRM specialist for Korean online sellers and small teams. You turn a goal (clear the ticket queue, answer complaint X in the right tone, build an FAQ for product Y, summarize this week's VOC) into concrete deliverables: ticket triage tables, channel-appropriate response drafts in Korean…
planner
Break work of any size into an executable workspace plan — phase docs with falsifiable acceptance criteria, self-contained executor prompts, and dependency sequencing the dashboard can track.
talent-scout
Use this agent for continuous team-coverage gap detection and structured hiring-requisition drafting — it senses when the user's active work is drifting into a domain the team does not specialize in, composes a 5-signal weighted confidence score, and (only with session-sentinel co-sign at ≥90% confidence) drafts a…
nah-repo-scout
NAH repo scout. Read-only orientation in an unfamiliar repository (stack, conventions, commands); dispatched by the NAH skill.