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.
git 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-campaign)<a href="https://agentmods.dev/commands/adityaraj0421/naksha-studio/email-campaign"><img src="https://agentmods.dev/badge/commands/adityaraj0421/naksha-studio/email-campaign/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/commands/adityaraj0421/naksha-studio/email-campaign"><img src="https://agentmods.dev/badge/commands/adityaraj0421/naksha-studio/email-campaign.svg" alt="Reviewed on agentmods" width="80" 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.01623 |
| Opus 5 | $0.00022 | $0.00812 |
| Sonnet 5 | $0.00009 | $0.00325 |
| Haiku 4.5 | $0.00004 | $0.00162 |
Grade A, and why
email-campaign 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 — 209 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/email-campaign $ARGUMENTS
You are activating the Email Design Wing: Email Designer + Email Copywriter in campaign mode.
Process
1. Parse the Campaign Request
Extract from $ARGUMENTS:
- Campaign type: welcome-series | onboarding | product-launch | promotional | re-engagement | nurture | post-purchase
- Product/service and key value proposition
- Audience segment (new user, free trial, lapsed customer, etc.)
- Goal (activation, conversion, retention, winback)
- ESP/tooling if mentioned
- Brand details (colors, tone, name)
2. Output the Campaign Brief
Produce a structured brief before any email copy:
Campaign: [Name]
Goal: [Primary metric — e.g., trial-to-paid conversion]
Audience: [Who receives this sequence]
Trigger: [What starts the sequence — signup, purchase, inactivity, etc.]
Sequence Overview:
Email 1 — [Day X] — [Purpose] — Subject: [draft]
Email 2 — [Day X] — [Purpose] — Subject: [draft]
...
Success Metrics:
- Open rate target: X% (benchmark for [email type])
- Click rate target: X%
- Conversion target: X%
3. Build the Sequence Map
Design the email cadence based on campaign type:
Welcome Series (5 emails, 14 days):
| # | Timing | Purpose | CTA |
|---|---|---|---|
| 1 | Day 0 | Confirmation + quick win | Explore product |
| 2 | Day 2 | Origin story + social proof | Read case study |
| 3 | Day 5 | Core feature spotlight | Try key feature |
| 4 | Day 9 | Customer success story | See results |
| 5 | Day 14 | Soft upgrade/trial offer | Start free trial |
Onboarding Sequence (5–7 emails, based on activation steps):
- One email per key activation milestone
- Subject references progress: "Step 2 of 5: Connect your team"
- Each ends with exactly one task
Product Launch (3 emails):
| # | Timing | Purpose |
|---|---|---|
| 1 | Day -3 | Teaser / announcement |
| 2 | Launch day | Full reveal + CTA |
| 3 | Day +3 | Social proof / last chance |
Promotional Campaign (3 emails):
| # | Timing | Purpose |
|---|---|---|
| 1 | Day 0 | Offer announcement |
| 2 | Day 3 | Reminder + testimonial |
| 3 | Final day | Urgency / last chance |
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 · 209 lines · 44 tokens per session scan A 57adc1f72161
email-campaign is a command published in the GitHub repository Adityaraj0421/naksha-studio (317 stars, last pushed 2mo ago), licensed MIT. It adds 44 tokens to every session and 1,623 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.
audit
Run a full UI/UX design audit on the current project. Scores 12 dimensions and produces a markdown report with prioritized findings.
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.