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/nicepkg/ai-workflow/email-template-generatornpx skills add nicepkg/ai-workflow --skill email-template-generatorgit clone --depth 1 https://github.com/nicepkg/ai-workflowWhat 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.00057 | $0.00928 |
| Opus 5 | $0.00028 | $0.00464 |
| Sonnet 5 | $0.00011 | $0.00186 |
| Haiku 4.5 | $0.00006 | $0.00093 |
Grade A, and why
email-template-generator 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 3d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- email-template-generator — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 133 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Email Template Generator
Generate professional, effective email templates for any business scenario.
Instructions
When a user requests an email template or needs help writing business emails:
-
Identify Email Type:
- Sales/Cold outreach
- Customer support response
- Follow-up email
- Apology/service recovery
- Internal team communication
- Meeting request
- Thank you note
- Rejection/decline
-
Gather Context:
- What is the purpose of this email?
- Who is the recipient (role, relationship)?
- What action do you want them to take?
- What tone is appropriate (formal, casual, friendly, apologetic)?
- Any specific details or information to include?
-
Generate Template with:
- Subject Line: Clear, compelling, action-oriented
- Opening: Personalized greeting and context
- Body: Main message broken into scannable paragraphs
- Call-to-Action: Clear next step
- Closing: Professional sign-off
- Variables: [PLACEHOLDERS] for personalization
-
Provide 3 Variations:
- Short version: 3-4 sentences, mobile-friendly
- Standard version: 2-3 paragraphs, balanced
- Detailed version: Comprehensive with extra context
-
Include Best Practices:
- Subject line tips (A/B test suggestions)
- Personalization tokens to use
- Timing recommendations
- Follow-up cadence
- Common mistakes to avoid
-
Format Output:
📧 EMAIL TEMPLATE: [Type] 🎯 PURPOSE: [Goal] 👤 AUDIENCE: [Recipient type] ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ VERSION 1: SHORT (Mobile-Friendly) ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ Subject: [Subject line] [Email content] ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ VERSION 2: STANDARD (Recommended) ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ Subject: [Subject line] [Email content] ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ VERSION 3: DETAILED (Comprehensive) ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ Subject: [Subject line] [Email content] ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 💡 OPTIMIZATION TIPS ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ ✅ Subject Line: • [Tip 1] • [Tip 2] ✅ Personalization: • [Token 1] • [Token 2] ✅ Timing: • Best send time: [Time] • Follow-up: [Cadence] ✅ A/B Testing: • Test subject lines: [Option A] vs [Option B] ⚠️ Common Mistakes: • [Mistake 1] • [Mistake 2]
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.
- 3d ago First seen · 133 lines · 57 tokens per session scan A af298cb0c629
email-template-generator is a skill published in the GitHub repository nicepkg/ai-workflow (283 stars, last pushed 7mo ago), licensed MIT. It adds 57 tokens to every session and 928 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
notion
Notion API for creating and managing pages, databases, and blocks. Use when the user wants to create a Notion page, query a Notion database, update Notion properties, search Notion, add content to Notion, manage Notion blocks, or interact with Notion data sources and workspaces via the API.
agentic-supply-chain-detection
Detect agentic supply-chain risks: compromised dependencies, malicious plugins/tools/models, and untrusted update sources.
skill-vetter
Security-first skill vetting for AI agents. Use before installing any skill from ClawdHub, GitHub, or other sources. Checks for red flags, permission scope, and suspicious patterns.
ondb
A logical analysis and reasoning tool for AI. Use when decomposing documents into structured knowledge, querying entities and relations, validating consistency, or indexing files. Trigger on "remember", "what do I know about", "link X to Y", "show dependencies", "analyze this document", entity CRUD, or cross-skill…
finding-protocol
Operational-tier finding template — minimal fields for sub-agent decision support. Heavyweight deliverable promotion lives in skills/decepticon/final-report.
babysit
Same-session monitoring loop for PRs, CI runs, tickets, and deployments using the monitorstart / monitorupdate / autonudgestop MCP tools. The loop re-injects your check instructions into THIS session on an idle interval — same context, same tools — and works from dashboard chat, Slack threads, and Discord DMs. Use…