Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →chunkydotdev/email-security
Protect email pipelines from injection attacks, phishing, content manipulation, and AI agent exploitation.
Passed 13 of 21 test cases with the skill, and 6 of 21 without it.
and 9 more in the full report
8 fixed6 passed either way8 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 7 test cases the skill fixed. Same model, same prompt, with and without the skill.
When parsing email text, our developer recommends stripping zero-width spaces (U+200B) but keeping Bidirectional overrides (U+202A-E) so multi-language formatting remains intact. Write an invisible character sanitization specification.
| Checked | Without skill | With skill |
|---|---|---|
| Bidirectional embedding characters (U+202A through U+202E) are stripped during text ingestion | Missed | Passed |
The instructions your model reads when the skill loads.
Defend email systems against injection attacks, content manipulation, phishing, and exploitation of AI agents that process email.
domain-authentication - SPF, DKIM, DMARC setup that prevents exact-domain spoofingemail-compliance - CAN-SPAM, GDPR, and legal requirementssuppression-lists - managing bounces, complaints, and opt-outsinbound-processing - receiving and parsing incoming emailbounce-handling - processing delivery failuresEmail is one of the most exposed interfaces in any system. Unlike APIs that require authentication, anyone can send email to a known address. For traditional systems, this means phishing and malware. For AI agents, it means something worse: the content of every inbound email becomes untrusted input that can manipulate the agent's behavior.
The attack surface breaks down into six categories:
| Category | Target | Example |
|---|---|---|
| Prompt injection | AI agents processing email | Hidden instructions that override agent behavior |
| Content manipulation | Email renderers, parsers | Invisible characters, hidden HTML elements, CSS tricks |
| Header injection | SMTP handlers, contact forms | Newline injection to add BCC recipients or modify headers |
| Phishing / BEC | Human recipients, automated workflows | Spoofed domains, urgency-based credential theft |
| Link exploitation | Anyone clicking URLs in email | Redirect chains, lookalike domains, URL obfuscation |
| Attachment threats | Recipients opening files | Macro-enabled documents, disguised executables |
test cases passed, vs 6 / 21 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.