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 opendatahub-io/ai-helpers --skill gmail-draftgit clone --depth 1 https://github.com/opendatahub-io/ai-helpersWrote 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/opendatahub-io/ai-helpers/gmail-draft)<a href="https://agentmods.dev/skills/opendatahub-io/ai-helpers/gmail-draft"><img src="https://agentmods.dev/badge/skills/opendatahub-io/ai-helpers/gmail-draft/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/opendatahub-io/ai-helpers/gmail-draft"><img src="https://agentmods.dev/badge/skills/opendatahub-io/ai-helpers/gmail-draft.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00053 | $0.00709 |
| Opus 5 | $0.00026 | $0.00354 |
| Sonnet 5 | $0.00011 | $0.00142 |
| Haiku 4.5 | $0.00005 | $0.00071 |
Grade A, and why
gmail-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 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 — 104 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Gmail Draft
Compose a Gmail draft from text content provided in the conversation.
Prerequisites
gwsbinary must be on$PATH- Authenticated with Gmail compose scope: run
gws auth login(not--readonly)
If gws is not installed or authentication fails, tell the user to follow the
setup instructions in the google-workspace skill.
Helper scripts are located in ${CLAUDE_SKILL_DIR} and require Python 3.10+.
Step 1: Gather Recipients, Subject, and Body
Collect the three required inputs. Sources depend on how the skill was invoked:
- From another skill (e.g.
email-meeting-summary): recipients, subject, and body are passed in context — use them directly. - Standalone invocation: use
AskUserQuestionto collect any that are missing:- Recipients: "Who should receive this email? (comma-separated addresses)"
- Subject: "What should the subject line be?"
- Body: "Paste or describe the content you want in the email body."
Step 2: Present for Review
Show the user the draft details before creating:
To: <recipients>
Subject: <subject>
<body>
Ask:
"Does this look right? Reply with any edits, or say 'send' to create the draft."
Incorporate edits and re-present until the user approves.
Step 3: Create the Draft
Write the body to a temp file, then call create_draft.py:
BODY_FILE=$(mktemp /tmp/gmail_draft_body.XXXXXX)
cat > "$BODY_FILE" << 'BODY_EOF'
<approved body text>
BODY_EOF
python3 "${CLAUDE_SKILL_DIR}/scripts/create_draft.py" \
--to "<recipients>" \
--subject "<subject>" \
--body-file "$BODY_FILE"
Step 4: Confirm
On success, tell the user:
"Draft created. You can find it in the Drafts folder in Gmail at https://mail.google.com/mail/#drafts. Review it before sending."
If the script exits with an error, show the error message and suggest the user
check gws auth login permissions (the Gmail scope must include draft
creation).
Error Reference
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.
- 9d ago First seen · 104 lines · 53 tokens per session scan A 72929dbfe192
gmail-draft is a skill published in the GitHub repository opendatahub-io/ai-helpers (37 stars, last pushed 2d ago), licensed Apache-2.0. It adds 53 tokens to every session and 709 once invoked, about $0.0003 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
quick-tasks
Token-saving mode for everyday lightweight work. Use for one-line fixes, typo/config-value changes, quick questions ("what does this function do?"), throwaway scripts, and anything that ends inside a single file. Output is a minimal diff and a short report. For multi-file, design, or new-feature work, switch to the…
Dispatching Parallel Agents
Concurrent execution of independent subtasks using multi-agent scheduling.
Executing Implementation Plans
Systematic execution of multi-step implementation plans with milestone verification.
selection-processor
Use when processing only a selected portion of text rather than a full file, to save tokens and enable targeted AI operations.
nft-standards
Implement NFT standards (ERC-721, ERC-1155) with proper metadata handling, minting strategies, and marketplace integration. Use when creating NFT contracts, building NFT marketplaces, or implementing digital asset systems.
postgresql-table-design
Use this skill when designing or reviewing a PostgreSQL-specific schema. Covers best-practices, data types, indexing, constraints, performance patterns, and advanced features.