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/adityaraj0421/naksha-studio/email-templategit clone --depth 1 https://github.com/Adityaraj0421/naksha-studioWrote 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/adityaraj0421/naksha-studio/email-template)<a href="https://agentmods.dev/commands/adityaraj0421/naksha-studio/email-template"><img src="https://agentmods.dev/badge/commands/adityaraj0421/naksha-studio/email-template.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.00044 | $0.01461 |
| Opus 5 | $0.00022 | $0.00731 |
| Sonnet 5 | $0.00009 | $0.00292 |
| Haiku 4.5 | $0.00004 | $0.00146 |
Grade A, and why
email-template 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.
How it starts
The opening of the file, as written. The whole thing — 169 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/email-template $ARGUMENTS
You are activating the Email Design Wing: Email Designer + Email Copywriter.
Process
1. Parse the Request
Extract from $ARGUMENTS:
- Email type: welcome | transactional | newsletter | promotional | onboarding | re-engagement | product-announcement
- Brand/product name and any colors/fonts mentioned
- Specific content (product name, offer, deadline, key features)
- ESP (if mentioned): Mailchimp, SendGrid, Klaviyo, HubSpot — defaults to generic
{{{VARIABLE}}}syntax
If the email type is ambiguous, default to promotional.
2. Write the Copy Brief
Before touching HTML, produce a copy brief:
Subject line: [< 50 chars, benefit-driven]
Preview text: [40–90 chars, complements subject]
Headline: [benefit-first H1 for hero]
Subheadline: [1 sentence supporting the headline]
Body: [2–3 short paragraphs, AIDA structure]
CTA text: [action + outcome, first-person optional]
Footer: [legal, unsubscribe, address placeholders]
3. Design the Layout
Choose the layout based on email type:
| Email Type | Layout |
|---|---|
| Welcome | Logo + Hero + 3 feature tiles + single CTA + footer |
| Transactional | Logo + summary card + data table + single CTA + footer |
| Newsletter | Logo + hero section + 2–4 content sections + footer |
| Promotional | Full-bleed hero + benefit bullets + deadline + CTA + footer |
| Onboarding | Progress bar + task card + single CTA + footer |
| Re-engagement | Minimal — personal tone, soft hero, soft CTA + unsubscribe prominent |
| Product announcement | Hero image + 3 feature tiles + CTA + footer |
Color defaults:
- Primary:
#2563eb(blue) - Text:
#111827(gray-900) - Background:
#f4f4f4 - Surface:
#ffffff
Use brand colors if specified in $ARGUMENTS.
4. Build the HTML
Produce complete, production-ready HTML following these rules:
Structure:
- Full
<!DOCTYPE html>document with MSO conditional comments - Preheader div (hidden, padded with
‌ ) - Wrapper table 100% width → inner container table
width="600"withclass="email-container" - Each section in its own
<tr><td>block
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 · 169 lines · 44 tokens per session scan A f9b3fbee546f
email-template is a command published in the GitHub repository Adityaraj0421/naksha-studio (316 stars, last pushed 2mo ago), licensed MIT. It adds 44 tokens to every session and 1,461 once invoked, about $0.0002 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 commands, from other repositories
brand
Generate a full editorial brand-guidelines book for any URL. 14 chapters covering brand essence/archetype, colour, typography, spacing, shape, iconography, motion, components, voice, accessibility, tokens, and how-to-use guidance. Print-ready, dark-mode toggle, hand-off-ready single HTML.
pack
Bundle every designlang output (DTCG tokens, Tailwind, shadcn, Figma vars, motion, anatomy, Storybook, prompts) into one polished design-system directory ready to zip and ship.
grade
Generate a shareable HTML "Design Report Card" — letter grade, 8 dimensions, evidence (palette, type, rhythm), strengths + fixes, plus an SVG badge.
design-enforce
Use when code has drifted off the design system. Raw hex values and pixel numbers written where a token already exists, one-off components, library defaults left untouched. Finds every bypass and fixes it.
design-grill
Use when a design keeps getting reinvented every session. Interviews you until you share one understanding, then writes the vocabulary and the binding decisions into the repo so they survive the next context window.
design-triage
Use when a dwic audit report is full of findings and there is no plan. Ranks them into an order someone can work through, then works through it.