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 provos/ironcurtain --skill email-formattinggit clone --depth 1 https://github.com/provos/ironcurtainWrote 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/provos/ironcurtain/email-formatting)<a href="https://agentmods.dev/skills/provos/ironcurtain/email-formatting"><img src="https://agentmods.dev/badge/skills/provos/ironcurtain/email-formatting/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/provos/ironcurtain/email-formatting"><img src="https://agentmods.dev/badge/skills/provos/ironcurtain/email-formatting.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00053 | $0.00450 |
| Opus 5 | $0.00026 | $0.00225 |
| Sonnet 5 | $0.00011 | $0.00090 |
| Haiku 4.5 | $0.00005 | $0.00045 |
Grade A, and why
email-formatting 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 10d 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.
What it actually says
Email formatting conventions
Use these conventions whenever you write a markdown file that summarizes email content.
Heading depth
- The document has exactly one
#heading at the top: the report title. - Each individual email gets a
##heading whose text is the email subject. - Do not use
###or deeper for per-email metadata; use a bullet list instead.
Per-email metadata
For each email, render metadata as an unordered list immediately under the
## subject heading, in this order:
From: <sender>To: <recipient(s), comma-separated>Date: <as it appears in the source, no reformatting>Summary: <1-2 sentences in prose>
Line length and whitespace
- Soft-wrap at roughly 80 columns. Don't hard-break inside a sentence.
- Exactly one blank line between sections; never two or more.
- No trailing whitespace at end of lines.
Emoji policy
Do not use emoji in summary documents. They render inconsistently across mail clients that may consume the markdown downstream.
Preamble and outro
There is no preamble (no "Here is the summary..." opener) and no outro
(no "Let me know if..." closer). The document opens with the # title.
Provenance footer (required)
The document MUST end with the literal HTML comment marker on a line by
itself, separated from the last email's Summary: bullet by exactly one
blank line:
<!-- email-summary/v1 -->
This marker is how downstream tooling identifies the generator and schema version. Producers that omit it are non-compliant; producers that change the spelling, casing, or version segment break parsers that depend on the literal string. Do not localize, prettify, or expand the marker — it is a machine-readable token, not human prose.
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.
- 10d ago First seen · 56 lines · 53 tokens per session scan A 4af5603dea43
email-formatting is a skill published in the GitHub repository provos/ironcurtain (602 stars, last pushed 5d ago), licensed Apache-2.0. It adds 53 tokens to every session and 450 once invoked, about $0.0003 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 skills, from other repositories
09-for-sure
Run an iterative agent loop that retries until a runnable success condition passes. Use when the user says "for sure", "keep trying until", or wants guaranteed completion against a success command. Not for one-shot tasks or uncheckable goals.
maintenance
Update mcp-reporter dependencies, adopt SDK changes, reconcile development workflows, and verify the CLI and library.
field-test
Exercise mcp-reporter's collected reports through in-memory, stdio, HTTP and compiled Node entry points.
ci-cd-pipeline
Design and implement CI/CD pipelines for automated testing and deployment.
test-driven-development
TDD workflow — Red, Green, Refactor cycle with practical examples.
resume-ai-validator
A command-line tool for testing ResumeAI, a service that analyzes and improves résumés. It checks both the service's API and the user interface through complete user journeys.