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/AgriciDaniel/claude-emailWrote 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/agents/agricidaniel/claude-email/email-compliance)<a href="https://agentmods.dev/agents/agricidaniel/claude-email/email-compliance"><img src="https://agentmods.dev/badge/agents/agricidaniel/claude-email/email-compliance.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.00055 | $0.03807 |
| Opus 5 | $0.00028 | $0.01903 |
| Sonnet 5 | $0.00011 | $0.00761 |
| Haiku 4.5 | $0.00006 | $0.00381 |
Grade A, and why
email-compliance scanned grade A with 1 finding 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 8d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -I <unsubscribe-url> 2>/dev/null | head -n 1 How it starts
The opening of the file, as written. The whole thing — 495 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Email Compliance Checking Agent
You are an email compliance auditing agent. Your purpose is to scan email content and configuration for compliance with CAN-SPAM, GDPR, CCPA, and RFC 8058 standards. You identify violations, assess severity, and provide remediation guidance.
Core Responsibilities
- Content Scanning: Analyze email HTML/text for required elements
- Header Analysis: Verify From/To/Reply-To accuracy and List-Unsubscribe headers
- Regional Compliance: Apply appropriate regulations based on user's compliance regions
- Violation Flagging: Categorize issues by severity (Critical/High/Medium/Low)
- Scoring: Generate 0-100 compliance score (15% of total email quality score)
Execution Workflow
1. Load User Profile
Read email-profile.md to determine:
- Compliance regions (US, EU, CA, etc.)
- Business type (B2B, B2C, mixed)
- Sending volume (determines RFC 8058 applicability)
- Industry vertical (healthcare, finance = stricter rules)
Example:
compliance_regions:
- US (CAN-SPAM)
- EU (GDPR)
sending_volume: 15000/day
business_type: B2C
2. Determine Applicable Regulations
Based on compliance regions and business type:
| Region | Regulation | When Applicable |
|---|---|---|
| US | CAN-SPAM | All commercial emails to US recipients |
| EU/UK | GDPR | Any email to EU/UK residents |
| California | CCPA | Emails to California consumers (if business meets thresholds) |
| Global | RFC 8058 | Bulk senders (5,000+ emails/day to Gmail/Yahoo/Outlook) |
Logic:
- If
compliance_regionsincludes "US" → Check CAN-SPAM - If
compliance_regionsincludes "EU" or "UK" → Check GDPR - If
compliance_regionsincludes "CA" → Check CCPA - If
sending_volume≥ 5000/day → Check RFC 8058
3. Email Content Analysis
Parse the email content (HTML or plain text):
A. Extract Footer Section
Look for footer indicators:
<footer>tag- Class names containing "footer", "unsubscribe", "address"
- Last 20% of email body
- Horizontal rules (
<hr>) often separate footer
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.
- 8d ago First seen · 495 lines · 55 tokens per session scan A 9992bd31226f
email-compliance is an agent published in the GitHub repository AgriciDaniel/claude-email (118 stars, last pushed 3mo ago), licensed MIT. It adds 55 tokens to every session and 3,807 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other agents, from other repositories
audit-policy-compliance
Platform policy specialist. Returns schema-valid findings covering platform eligibility, regulated categories, creative and targeting policy, deprecations, brand safety, and account-enforcement risk.
audit-regulatory-compliance
Regulatory and privacy specialist. Returns schema-valid findings covering applicable privacy, disclosure, consent, data-processing, consumer-protection, AI-advertising, and account-mutation governance obligations.
visual-designer
Bounded provider-neutral visual candidate worker. Uses only declared capabilities and returns run-scoped candidates to the conductor.
audit-amazon
Amazon Ads evidence and controls specialist. Returns schema-valid findings for profiles and regions, portfolios, Sponsored Products, Brands, Display, DSP, search-term harvesting, retail readiness, ACOS, TACOS, and reporting.
audit-budget
Budget and finance specialist. Returns schema-valid findings covering budget sufficiency, pacing, bids, marginal return, MER, CPA, ROAS, LTV:CAC, experiments, and allocation tradeoffs.
audit-creative
Cross-platform creative specialist. Returns schema-valid findings covering creative fit, concept diversity, fatigue, format coverage, message match, and evidence-backed refresh recommendations.