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/maigentic/stratartsWrote 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/maigentic/stratarts/email-marketing-architect)<a href="https://agentmods.dev/commands/maigentic/stratarts/email-marketing-architect"><img src="https://agentmods.dev/badge/commands/maigentic/stratarts/email-marketing-architect/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/maigentic/stratarts/email-marketing-architect"><img src="https://agentmods.dev/badge/commands/maigentic/stratarts/email-marketing-architect.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.00035 | $0.15134 |
| Opus 5.5 | $0.00014 | $0.06054 |
| Sonnet 5.5 | $0.00007 | $0.03027 |
| Haiku 4.5 | $0.00003 | $0.01513 |
Grade A, and why
email-marketing-architect 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 1mo 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 — 1,934 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Email Marketing Architect
Step 0: Pre-Generation Verification
Before generating any output, verify these template requirements:
Template Location
- Skeleton Template:
html-templates/email-marketing-architect.html - Test Output Reference:
skills/marketing-growth/email-marketing-architect/test-template-output.html
Required Placeholders to Replace
{{PRODUCT_NAME}}- Business/product name{{SUBTITLE}}- Strategy summary tagline{{DATE}}- Generation date{{CAMPAIGN_COUNT}}- Number of automated campaigns{{TOTAL_EMAILS}}- Total automated emails in system{{INTERPRETATION_TITLE}}- Score interpretation headline{{INTERPRETATION_TEXT}}- Detailed score explanation{{VERDICT}}- Overall assessment badge{{GOALS_DESCRIPTION}}- Goals section intro text{{GOAL_CARDS}}- 3 goal cards HTML{{JOURNEY_STAGES}}- 5 journey stage HTML blocks{{CAMPAIGN_CARDS}}- Drip campaign HTML blocks{{SEGMENT_CARDS}}- 3 segment cards HTML{{WORKFLOW_CARDS}}- 4 workflow cards HTML{{GUIDELINE_CARDS}}- 4 copywriting guideline cards HTML{{METRIC_CARDS}}- 4 metric cards HTML{{ROADMAP_PHASES}}- 3 phase cards HTML{{CONTEXT_SIGNATURE}}- Unique session identifier
Chart Data Placeholders
{{JOURNEY_LABELS}}- Journey stage names for charts{{JOURNEY_CONVERSION_DATA}}- Conversion rates per stage{{EMAIL_VOLUME_DATA}}- Emails per journey stage{{SEGMENT_LABELS}}- Segment names{{SEGMENT_DATA}}- Segment percentages{{SEGMENT_OPEN_DATA}}- Open rates by segment{{SEGMENT_CLICK_DATA}}- Click rates by segment{{PROJECTION_DATASETS}}- Performance projection data
Canonical CSS Patterns (MUST match exactly)
- Header:
header { background: #0a0a0a; padding: 0; ... }+.header-content { ... max-width: 1600px; background: linear-gradient(135deg, #10b981 0%, #14b8a6 100%); padding: 4rem 4rem 3rem 4rem; ... } - Score Banner:
.score-banner { background: #0a0a0a; padding: 0; ... }+.score-container { display: grid; grid-template-columns: auto 1fr auto; ... max-width: 1600px; ... } - Footer:
footer { background: #0a0a0a; ... }+.footer-content { max-width: 1600px; ... }
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.
- 1mo ago First seen · 1,934 lines · 35 tokens per session scan A f3f613d5d5a5
email-marketing-architect is a command published in the GitHub repository maigentic/stratarts (45 stars, last pushed 8mo ago), licensed MIT. It adds 35 tokens to every session and 15,134 once invoked, about $0.0001 per session on Opus 5.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
psql-query
Run ad-hoc PostgreSQL analytics queries against dev/test database.
setup
Connect your Firecrawl account and check that the Firecrawl tools respond.
build
Mini spec-first development workflow for well-scoped implementation tasks with human in the loop.
esp-teach
One-time project setup -- discover hardware, find datasheets, persist context to CLAUDE.md.
swift-critique
Critique SwiftUI code for patterns, design, clean code, accessibility, and performance.
fec-smell
Diagnose frontend code smells with evidence and candidate refactorings without changing business code.