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 agentmods add skills/ginkida/rustyhand/email-writernpx skills add ginkida/rustyhand --skill email-writergit clone --depth 1 https://github.com/ginkida/rustyhandWrote 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/ginkida/rustyhand/email-writer)<a href="https://agentmods.dev/skills/ginkida/rustyhand/email-writer"><img src="https://agentmods.dev/badge/skills/ginkida/rustyhand/email-writer.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.00018 | $0.00713 |
| Opus 5 | $0.00009 | $0.00357 |
| Sonnet 5 | $0.00004 | $0.00143 |
| Haiku 4.5 | $0.00002 | $0.00071 |
Grade A, and why
email-writer 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 6d 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.
This is a copy
100% identical to email-writer — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 39 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Professional Email Writer
A business communication specialist with deep expertise in crafting clear, effective, and appropriately toned emails for professional contexts. This skill provides guidance for structuring emails that get read, understood, and acted upon, whether writing to executives, clients, teammates, or external partners across cultures and communication styles.
Key Principles
- Lead with the bottom line up front (BLUF): state the purpose, decision needed, or key information in the first sentence so the reader immediately knows why this email matters
- Match your tone to the relationship and context; an update to your team reads differently than a request to a VP or a negotiation with a vendor
- Make the ask explicit and actionable; every email that requires a response should state exactly what is needed and by when
- Keep emails scannable with short paragraphs, bullet points, and bold key phrases; most recipients scan on mobile before deciding to read in full
- Respect inbox volume by consolidating related points into one email rather than sending multiple messages in rapid succession
Techniques
- Write subject lines that convey both topic and urgency: "Decision needed by Friday: Q3 budget allocation" is actionable, "Quick question" is not
- Structure longer emails with sections: Context (1-2 sentences of background), Details (bullet points or numbered items), and Ask (clear next steps with deadlines)
- Calibrate formality based on recipient: "Hi Alex" for peers, "Dear Dr. Chen" for formal external contacts, and match the tone the other party sets in their replies
- Use CC intentionally: include people who need visibility, use BCC only for large distribution lists, and explain in the body why recipients are included if it is not obvious
- Handle difficult conversations (delays, rejections, disagreements) with empathy-first framing: acknowledge the situation, explain the reasoning, and offer an alternative or next step
- Set follow-up expectations: if you need a response, state the deadline; if no response is needed, say "No reply needed, just keeping you informed"
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.
- 6d ago First seen · 39 lines · 18 tokens per session scan A dcab12c0eeec
email-writer is a skill published in the GitHub repository ginkida/rustyhand (20 stars, last pushed 25d ago), licensed MIT. It adds 18 tokens to every session and 713 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to email-writer, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
hive.browser-automation
Required before any hive-browser CLI command. The browser is driven from the terminal by running hive-browser ... --json via terminalexec — not via MCP tools. Teaches the browser lifecycle rules (the bridge attaches to the USER'S running Chrome — never kill or launch browser processes; timeouts are transport issues…
hive.linkedin-automation
Read before automating LinkedIn with browser tools. LinkedIn combines shadow DOM (#interop-outlet), strict Trusted Types CSP that silently drops innerHTML, Lexical composer, native beforeunload dialogs that hang the bridge, and aggressive spam filters — each has bitten us at least once. Verified flows for profile…
hive.worker-delegation
Concrete patterns for breaking colony work into parallel worker jobs via runplaybook — when fan-out helps, how to model the goal as a tracker table, write the worker skill, author the playbook, pilot, and let convergence retry/resume the gap.
hive.x-automation
Read before automating X / Twitter with browser tools. Verified flows for post, reply, delete, search-and-engage, plus the Draft.js compose quirks that silently disable the send button. Includes the daily-reply and job-market-reply playbooks. Requires hive.browser-automation for the underlying screenshot + coordinate…
hive.slack-notifications-setup
Set up a Slack notification channel (Sentinel) for a colony by driving the browser — reuse or create the "Hive Sentinel" Slack app from a JSON manifest, install it, capture the bot + app tokens, create/select the channel via the Slack API, and turn Sentinel on so the colony can ping the user on Slack and accept…
hive.writing-hive-skills
Author a new Agent Skill for a Hive agent that conforms to the Agent Skills specification (SKILL.md with YAML frontmatter, optional scripts/references/assets directories). Use when the user asks to create, scaffold, add, or package a new skill for a Hive agent.