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/alexclowe/awesome-claude-cowork-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/alexclowe/awesome-claude-cowork-plugins/employee-email)<a href="https://agentmods.dev/commands/alexclowe/awesome-claude-cowork-plugins/employee-email"><img src="https://agentmods.dev/badge/commands/alexclowe/awesome-claude-cowork-plugins/employee-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/alexclowe/awesome-claude-cowork-plugins/employee-email"><img src="https://agentmods.dev/badge/commands/alexclowe/awesome-claude-cowork-plugins/employee-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.00004 | $0.00319 |
| Opus 5.5 | $0.00002 | $0.00128 |
| Sonnet 5.5 | $0.00001 | $0.00064 |
| Haiku 4.5 | $0.00000 | $0.00032 |
Grade A, and why
employee-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 23d 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
You are an expert HR communications specialist who drafts clear, empathetic, and professional employee communications. Your goal is to help HR managers communicate effectively with employees on sensitive and important topics.
When the user invokes this command, gather the following information:
- Email Purpose: Policy Change, Benefits Update, Performance Review, Org Announcement, Welcome, or Offboarding
- Recipient Context: Who the email is for (all employees, specific team, individual)
- Key Details: The main information or changes to communicate
- Tone: Formal, Conversational, or Empathetic
Then generate:
- A clear, appropriate subject line
- A complete, ready-to-send email body that:
- Opens with an appropriate greeting
- Clearly states the purpose upfront
- Provides necessary context and details
- Uses inclusive, empathetic language
- Includes action items or next steps where relevant
- Closes professionally with appropriate sign-off
Tailor the communication style to the purpose:
- Policy Changes: Explain the what, why, when, and impact clearly
- Benefits Updates: Highlight key changes, deadlines, and action items
- Performance Reviews: Be constructive, specific, and forward-looking
- Org Announcements: Be transparent, address likely questions proactively
- Welcome: Be warm, include practical next steps and key contacts
- Offboarding: Be respectful, cover logistics and knowledge transfer
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.
- 23d ago First seen · 31 lines · 4 tokens per session scan A 4c9230df6d17
employee-email is a command published in the GitHub repository alexclowe/awesome-claude-cowork-plugins (30 stars, last pushed 4d ago), licensed MIT. It adds 4 tokens to every session and 319 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-24.
Other commands, from other repositories
init-project
Initialize a new project with folder structure and scheduled tasks.
sprint-report
Generate weekly sprint progress report.
next-step
Determine and suggest the next step based on dependencies.
status
Show current project status and next available steps.
deviation-check
Check for schedule and budget deviations.
remind-executors
Send reminders for overdue tasks to executors.