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 iamwaqargulzar/Marketing-Agent-OS --skill email-render-buildergit clone --depth 1 https://github.com/iamwaqargulzar/Marketing-Agent-OSWrote 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/iamwaqargulzar/marketing-agent-os/email-render-builder)<a href="https://agentmods.dev/skills/iamwaqargulzar/marketing-agent-os/email-render-builder"><img src="https://agentmods.dev/badge/skills/iamwaqargulzar/marketing-agent-os/email-render-builder/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/iamwaqargulzar/marketing-agent-os/email-render-builder"><img src="https://agentmods.dev/badge/skills/iamwaqargulzar/marketing-agent-os/email-render-builder.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.00113 | $0.00813 |
| Opus 5 | $0.00056 | $0.00407 |
| Sonnet 5 | $0.00023 | $0.00163 |
| Haiku 4.5 | $0.00011 | $0.00081 |
Grade A, and why
email-render-builder 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 5d 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.
This is a copy
67% identical to impeccable — 318 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 76 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Email Render Builder
Quick Start
Use this skill for email render builder. Start from the user’s concrete objective and available evidence; do not substitute generic marketing advice for task-specific analysis.
Skill Contract
- Reads: user-provided context; relevant project files;
.agents/product-marketing.mdwhen present; approved public or connected data sources. - Writes: recommendations and artifacts in the response by default. Persistent file/account changes require explicit request or authorization.
- Evidence: label consequential claims as
measured,user-provided,calculated,estimated, orproxy. Never upgrade uncertainty silently. - Side effects: do not publish, send, spend, delete, mutate accounts, or persist registry truth without user authorization.
- Freshness: verify current platform rules, search eligibility, ad policies, model/tool capabilities, laws, pricing, and other time-sensitive claims before acting.
Instructions
- Define the exact
email render builderobjective, audience/scope, constraints and success metric before recommending action. - Load shared product-marketing context when it materially changes the answer; ask only for missing facts that block a decision.
- Collect the minimum evidence needed for email render builder. Distinguish direct observations from assumptions and proxies.
- Execute the email render builder analysis or artifact using the domain checklist below; prefer specific outputs over generic best-practice lists.
- Prioritize actions by impact, confidence, effort and dependency. Identify what would falsify important assumptions.
- For external side effects, publishing, sending, spend changes, account changes or persistent writes, obtain authorization first.
- Finish with decision-ready output, evidence labels, open loops, and no more than three next-best skills.
Domain Checklist
- Lifecycle state
- Consent and compliance
- Segmentation
- Message objective
- Deliverability/channel constraints
- Sequence timing
- Personalization inputs
- Experiment metric
- Suppression/exit logic
What ships with it
4 files 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.
- 5d ago First seen · 76 lines · 113 tokens per session scan A ec119e361a33
email-render-builder is a skill published in the GitHub repository iamwaqargulzar/Marketing-Agent-OS (3 stars, last pushed 6d ago), licensed Apache-2.0. It adds 113 tokens to every session and 813 once invoked, about $0.0006 per session on Opus 5. A static security scan graded it A with 0 findings. It is 67% identical to impeccable, differing in 318 lines, and is treated as a copy.
Other skills, from other repositories
image-seo-audit
Audit every image on a page for SEO, performance, and accessibility — alt text quality, tiered file-size thresholds, WebP/AVIF format adoption, srcset/sizes responsiveness, lazy loading, fetchpriority on the LCP image, and width/height for CLS — producing an optimization list sorted by file-size savings. Triggers on…
landing-page-audit
Audit a landing page across six conversion dimensions — above-fold clarity, trust signals, form friction, message match against the upstream ad or email, page speed, and mobile experience — each scored 1-10, rolled into an overall score benchmarked against industry averages, with the top 5 fixes ranked by expected…
seo-growth
End-to-end SEO operations for B2B SaaS organic visibility. Use this skill when you need keyword research, technical SEO audits, content optimization, link building strategy, international expansion, AI/AEO optimization, schema markup, Core Web Vitals improvements, and organic traffic growth planning. Also triggers on…
visual-diff
Visual Regression Testing — screenshot comparison before and after changes. Use when user wants to check for visual regressions, compare UI changes, or verify CSS/layout changes didn't break anything.
ui-motion-workflow
Orchestrate UI direction, composition, motion provider selection, implementation, and browser-proven quality for polished frontend work. Use when Codex needs to improve a visual surface with animation or interactive polish; when a request mixes design intent, component choice, browser validation, accessibility, or…
kaicalls-design
Build KaiCalls-compliant UI components and pages using the KaiCalls design system. Use when creating new dashboard pages, components, forms, tables, cards, badges, or any UI within the KaiCalls admin panel. Ensures dark-first aesthetic, proper color tokens, typography classes, motion standards, and B2B SaaS best…