Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add Elnora-AI/elnora-google-workspace/plugin install google-workspaceWrote 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/elnora-ai/elnora-google-workspace/draft-email)<a href="https://agentmods.dev/commands/elnora-ai/elnora-google-workspace/draft-email"><img src="https://agentmods.dev/badge/commands/elnora-ai/elnora-google-workspace/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.1 | $0.00033 | $0.02553 |
| Opus 5 | $0.00016 | $0.01277 |
| Sonnet 5 | $0.00007 | $0.00511 |
| Haiku 4.5 | $0.00003 | $0.00255 |
Grade A, and why
draft-email scanned grade A with 1 finding 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 5d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
| URL — internal/company page | Verify it exists by `curl -sI` or `WebFetch`. **Zero tolerance** for unverified links. | How it starts
The opening of the file, as written. The whole thing — 218 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Draft Email: $ARGUMENTS
Task
Draft a Gmail email — either a reply to an existing thread (<thread-id>) or a new email to someone (<recipient-email> [topic]) — in your voice, with full context loaded and every claim verified.
This skill creates a Gmail DRAFT only. Never sends. The user reviews and approves before any send — never send without explicit approval.
Hard preconditions
You MUST complete every step in order. Skipping is not allowed.
Step 1 — Load your writing-voice guide (optional)
If your knowledge base has a writing-voice guide, load it and apply it. If there's none, skip this step and draft in a clear, professional default voice — the command must still work with no voice doc.
If you have a voice guide, pay particular attention to:
- Any at-a-glance / quick-reference section — banned phrases, banned punctuation, hard safety rules. This is the 90% of the catch.
- The relevant by channel subsection (cold outreach / inbound consulting / professional contacts / etc.) for the email type you're drafting.
- The core voice principles if drafting more than a one-liner.
If your knowledge base is configured (.claude/knowledge-base.local.md), the guide typically lives under {vault_path}/{company_dir}/ — resolve the path from that config.
Step 2 — Identify the recipient(s) and load CRM context
If a thread-id was passed:
python3 ${CLAUDE_PLUGIN_ROOT}/cli/gw.py gmail get-thread <thread-id> --compact
Extract the external participant(s) (sender + non-internal Cc). For each one:
- Look them up in
vault: {crm_dir}/contacts.csvby email. If found, capture: slug, full name, role, company, stage, last_contact_date, last_contact_channel, last_meeting_date, next_action, priority, notes. - Look up their company in
vault: {crm_dir}/companies.csvby name. Capture: slug, stage, NTE/billed/remaining (KPI columns), notes. - If their company stage is
active-customerorcustomer, also read the CRM's company/account detail file (its per-company Markdown file) for the rich relationship context (current state, open contracts, recent invoices, timeline, open items).
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.
- 5d ago First seen · 218 lines · 33 tokens per session scan A 0ef0531e2b05
draft-email is a command published in the GitHub repository Elnora-AI/elnora-google-workspace (2 stars, last pushed 4d ago), licensed Apache-2.0. It adds 33 tokens to every session and 2,553 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other commands, from other repositories
google-workspace-setup
One-time setup for the google-workspace-mcp plugin — check prerequisites, create/locate the OAuth client, define accounts, authorize each in the right browser, and wire it into the current project.
/openspec-apply
Implement an approved OpenSpec change and keep tasks in sync.
/openspec-archive
Archive a deployed OpenSpec change and update specs.
/openspec-proposal
Scaffold a new OpenSpec change and validate strictly.
proposal
name: OpenSpec: Proposal description: Scaffold a new OpenSpec change and validate strictly. category: OpenSpec tags: [openspec, change].
archive
name: OpenSpec: Archive description: Archive a deployed OpenSpec change and update specs. category: OpenSpec tags: [openspec, archive].