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 KirKruglov/claude-project-manager --skill send-emailgit clone --depth 1 https://github.com/KirKruglov/claude-project-managerWrote 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/kirkruglov/claude-project-manager/send-email)<a href="https://agentmods.dev/skills/kirkruglov/claude-project-manager/send-email"><img src="https://agentmods.dev/badge/skills/kirkruglov/claude-project-manager/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/skills/kirkruglov/claude-project-manager/send-email"><img src="https://agentmods.dev/badge/skills/kirkruglov/claude-project-manager/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.00200 | $0.01887 |
| Opus 5 | $0.00100 | $0.00944 |
| Sonnet 5 | $0.00040 | $0.00377 |
| Haiku 4.5 | $0.00020 | $0.00189 |
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 9d 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.
How it starts
The opening of the file, as written. The whole thing — 169 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: send-email
Internal service skill for sending project emails via Gmail MCP. Called exclusively by other agent skills — not directly by the user. Receives a rendered email from the calling skill, applies autonomy level rules, converts attachments if needed, and delivers via Gmail or saves a fallback draft.
Activation Context
This skill is activated when another agent skill instructs Claude to send an email. The calling skill provides all content; send-email handles delivery, autonomy logic, and fallback.
Calling skills: generate-questionnaire, generate-approval-letter, monitor-progress, coordinate-meeting, coordinate-executors.
Language Detection
Determine language from project-state.md field language. If absent: scan project artifacts for Cyrillic → RU. Default: EN.
Input
Parameters passed by the calling skill:
| Parameter | Required | Description |
|---|---|---|
email_type |
yes | E1–E8 (email type from artifacts registry) |
to |
yes | Recipient email(s) |
subject |
yes | Email subject (already filled by caller) |
body_md |
yes | Email body in Markdown (already rendered by caller) |
autonomy_level |
yes | 1 / 2 / 3 |
attachments |
no | File paths (.md, .xlsx) |
convert_to_docx |
no | Convert .md attachments to .docx. Default: false |
cc_pm |
no | PM email for Level 2 (if absent — read from project-state.md) |
Output
| Result | Path | Condition |
|---|---|---|
| Email sent via Gmail | — (external) | Level 1/2, Gmail available; Level 3 confirmed |
drafts/email-draft-{type}-{YYYY-MM-DD}.md |
drafts/ |
Level 3 pending; Gmail unavailable |
Log entry in logs/log.md |
logs/ |
Always |
Instructions
Step 1 — Guard-rail
If called directly by a user (not as part of a skill chain):
Detection: input is natural language without structured parameters — at least one of email_type, to, subject, body_md, autonomy_level is absent.
Respond: "send-email is an internal service skill activated automatically during email delivery. To send a project email, trigger the relevant skill (e.g., coordinate-executors for reminders, generate-approval-letter for approvals)."
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.
- 9d ago First seen · 169 lines · 200 tokens per session scan A 062ad07ce8ec
send-email is a skill published in the GitHub repository KirKruglov/claude-project-manager (6 stars, last pushed 4mo ago), licensed MIT. It adds 200 tokens to every session and 1,887 once invoked, about $0.0010 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-08-31.
Other skills, from other repositories
powerpoint-cli
PowerPoint CLI automation skill for Windows presentations. Use when a coding agent needs token-efficient, scriptable, or unattended PowerPoint automation via pptcli commands. Best for CI/CD, scheduled jobs, batch processing, PowerShell workflows, and bulk deck edits. Supports slides, shapes, text frames, tables…
github-flow-for-claude-on-web
Complete GitHub workflow for Claude Code on the web. ALL GitHub operations MUST use REST API (never gh CLI). Includes branch naming (claude/-sessionId), push retry logic, PR/issue management via API, and complete workflows. Use for all GitHub interactions in Claude Code web environment.
vibing-orchestrate
A coordinator for splitting independent tasks among separate vibing.nvim chats, a Neovim interface for working with coding agents, and combining their results.
self-testing
E2E self-testing workflow for vibing.nvim using a separate Neovim instance controlled over RPC. Use when writing or debugging E2E tests, running npm run test:e2e, or executing the 3-try auto-fix rule after implementing a feature. Covers the…
test-design
Automatically design comprehensive E2E test cases for newly implemented vibing.nvim features. Use immediately after completing feature implementation (Phase 5.4) and before running E2E tests. Generates test scenarios covering Happy paths, Error cases, Edge cases, and Integration points with priority ranking…
vibing-chat-search
A search tool for finding earlier vibing.nvim conversations by topic. It searches chat files for words and phrases, then checks the matching conversations for relevance.