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 mishahanin/heading-os --skill email-draftgit clone --depth 1 https://github.com/mishahanin/heading-osWrote 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/mishahanin/heading-os/email-draft)<a href="https://agentmods.dev/skills/mishahanin/heading-os/email-draft"><img src="https://agentmods.dev/badge/skills/mishahanin/heading-os/email-draft.svg" alt="Measured on agentmods" 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.00102 | $0.00770 |
| Opus 5 | $0.00051 | $0.00385 |
| Sonnet 5 | $0.00020 | $0.00154 |
| Haiku 4.5 | $0.00010 | $0.00077 |
Grade A, and why
email-draft 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 7d 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
Email Draft
Draft an outbound CEO email from Misha Hanin.
Variables
to: [Recipient name, title, company]
purpose: [What this email is trying to accomplish]
key_points: [Main points to cover — list them]
tone: formal | warm | direct | urgent — default: warm-direct
context: [Any specific relationship or situational context]
Instructions
Before drafting, read:
reference/misha-voice.md— Voice guide, especially Email sectioncontext/people.md— Check if recipient is listed; load relationship contextcontext/business-info.md— Load relevant 31C context for the email topic
Draft an email that:
- Opens directly — reference the reason for writing in the first sentence
- Covers key points in the right order (most important first)
- Uses one idea per paragraph, 2-3 lines max per paragraph
- Closes with a clear next step or invitation
- Matches tone to recipient (peer-level with CEOs, respectful with government, warm with Tribe)
Voss layer: Apply per .claude/rules/voss.md (always-active rule). Skill-specific hooks: calibrated questions for requests, labeling before addressing tension, "That's Right" summaries on negotiation follow-ups. Full framework: reference/voss-negotiation.md.
After the draft, provide:
- 2-3 subject line options
- Any relationship notes from people.md if relevant
- One flag: anything sensitive to review before sending
NEVER
- "I hope this email finds you well."
- "Dear Valued Partner,"
- "I am writing to inform you..."
- "Please don't hesitate to contact me."
- Passive voice where active works
- Burying the ask in the middle
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 7d ago First seen · 86 lines · 102 tokens per session scan A bd0d3f0e405e
email-draft is a skill published in the GitHub repository mishahanin/heading-os (11 stars, last pushed yesterday), licensed Apache-2.0. It adds 102 tokens to every session and 770 once invoked, about $0.0005 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-30.
Other skills, from other repositories
shogun-bloom-config
An interactive wizard that creates model-routing settings from your AI subscription choices. Model routing decides which available model handles each kind of task.
shogun-model-list
A reference table of AI command-line tools, their available models, subscription requirements, and maximum Bloom capability levels. Bloom's Taxonomy is a scale describing thinking tasks, from remembering information to creating new designs.
shogun-model-switch
A live-switching tool for changing which command-line AI agent, model, and reasoning mode is running. It updates settings, restarts the agent, and refreshes the displayed session information.
shogun-screenshot
A screenshot tool for getting images from a computer or web page and then cropping, resizing, or masking sensitive information. Playwright is a browser-automation tool used here to capture web pages.
shogun-readme-sync
A skill that compares an English README with its Japanese counterpart and brings them back into alignment. A README is the project document that explains what the software is and how to use it.
shogun-agent-status
A skill that shows whether the agents in a multi-agent Japanese feudal-themed team are working, waiting, missing, or assigned tasks. It combines terminal session status, task files, and unread messages.