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 commands/harperreed/office-admin-claude/draft-emailgit clone --depth 1 https://github.com/harperreed/office-admin-claudeWrote 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/harperreed/office-admin-claude/draft-email)<a href="https://agentmods.dev/commands/harperreed/office-admin-claude/draft-email"><img src="https://agentmods.dev/badge/commands/harperreed/office-admin-claude/draft-email.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 | $0.00000 | $0.00581 |
| Opus 5 | $0.00000 | $0.00291 |
| Sonnet 5 | $0.00000 | $0.00116 |
| Haiku 4.5 | $0.00000 | $0.00058 |
Grade A, and why
draft-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 4d 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
Draft an email in your personal style with guided assistance. Use the office:email-management skill.
Workflow:
-
Ask clarifying questions:
- Who is this email to? (name or email address)
- Is this a reply to an existing email? (yes/no)
- What's the main purpose? (scheduling, confirming, declining, requesting, etc.)
-
If replying to existing email:
- Search for the original email thread
- Get thread ID, message ID, and recipient email
- Read original email for context
-
If calendar-related (scheduling):
- Use office:calendar-management skill to check availability
- Include specific available times in draft
- Note any conflicts that need to be resolved
-
Draft the email:
- Load user's style from
~/.claude/office-admin-config.json - Match their tone, formality, and response length preferences
- Use their common phrases from config
- Apply signature preference (none/minimal/full)
- CRITICAL: Always include explicit
To:email address
- Load user's style from
-
Create the draft:
- Save as DRAFT (never send)
- Ensure proper threading if reply
- Verify subject line is appropriate
- Provide link to draft for user review
-
Post-draft actions:
- If email contains event info, offer to add to calendar
- If mentioning a new contact, offer to add to CRM
- Summarize what was created
Example interaction:
User: /draft-email
Claude: I'll help you draft an email. Let me ask a few questions:
1. Who is this email to? (name or email address)
2. Is this a reply to an existing email?
3. What's the main purpose? (scheduling, confirming, declining, requesting, etc.)
User: It's a reply to Sarah about scheduling a call next week
Claude: Let me search for Sarah's email... Found it!
I see Sarah asked about scheduling a call to discuss the Q1 project.
Let me check your calendar for next week...
You're available:
- Monday 2:00pm-4:30pm
- Tuesday 9:30am-12:00pm, 1:30pm-4:30pm
- Wednesday 10:00am-12:00pm
I'll draft a reply in your ultra-terse style:
---
**DRAFT CREATED:**
To: [email protected]
Subject: Re: Q1 Project Call
that works perfect. tuesday 2pm?
---
Draft saved to Gmail. Would you like me to:
- Add this to your calendar as a hold?
- Adjust the wording?
- Send it now?
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.
- 4d ago First seen · 77 lines · 0 tokens per session scan A f69b37076725
draft-email is a command published in the GitHub repository harperreed/office-admin-claude (5 stars, last pushed 9mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 581 tokens. 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 commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.