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/commands/fakoli/fakoli-plugins/send-email)<a href="https://agentmods.dev/commands/fakoli/fakoli-plugins/send-email"><img src="https://agentmods.dev/badge/commands/fakoli/fakoli-plugins/send-email/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/commands/fakoli/fakoli-plugins/send-email"><img src="https://agentmods.dev/badge/commands/fakoli/fakoli-plugins/send-email.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.00007 | $0.00241 |
| Opus 5.5 | $0.00003 | $0.00096 |
| Sonnet 5.5 | $0.00001 | $0.00048 |
| Haiku 4.5 | $0.00001 | $0.00024 |
Grade A, and why
send-email 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
/send-email
Send an email using the gws CLI.
Instructions
-
Parse the user's argument for recipient(s) and subject. If not provided, ask the user for:
- To: recipient email address(es)
- Subject: email subject line
- Body: email body content
-
First run with
--dry-runto show what will be sent:gws gmail +send --to <EMAILS> --subject '<SUBJECT>' --body '<BODY>' --dry-run -
Show the user the dry-run output and ask for confirmation.
-
On confirmation, run the actual send command (remove
--dry-run). -
Report success with the message ID.
Options
- Add
--ccor--bccif the user mentions CC/BCC recipients - Add
--htmlif the user provides HTML content - For attachments, explain that the raw API must be used instead
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 · 33 lines · 7 tokens per session scan A 72710dd4d40b
send-email is a command published in the GitHub repository fakoli/fakoli-plugins (4 stars, last pushed 27d ago), licensed MIT. It adds 7 tokens to every session and 241 once invoked, about $0.0000 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 commands, from other repositories
psalm
Command "psalm" from Marcel-Bich/marcel-bich-claude-marketplace, covering credo - the preacher's guide, step 0: run setup (recommended), entry point, credo's own teachings and topic: the credo workflow (end to end).
versioning
Universal version file discovery and sync. Works with any project structure.
watch
You are executing the /hydra:watch command. Live monitoring of all background agents with real-time status updates.
update
You are executing the /import:update command. Re-fetch documentation from original sources.
spawn
You are executing the /hydra:spawn command. Start an agent in an existing worktree.
explain
Explain the subject in depth using the fixed four-part structure: What, Why, Example, Consequences. Treat the subject as the thing to be explained, not as a literal question.