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 bobadilla-tech/requiems-api-skills --skill email-normalize-post-normalizegit clone --depth 1 https://github.com/bobadilla-tech/requiems-api-skillsWrote 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/bobadilla-tech/requiems-api-skills/email-normalize-post-normalize)<a href="https://agentmods.dev/skills/bobadilla-tech/requiems-api-skills/email-normalize-post-normalize"><img src="https://agentmods.dev/badge/skills/bobadilla-tech/requiems-api-skills/email-normalize-post-normalize/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/bobadilla-tech/requiems-api-skills/email-normalize-post-normalize"><img src="https://agentmods.dev/badge/skills/bobadilla-tech/requiems-api-skills/email-normalize-post-normalize.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.00027 | $0.00497 |
| Opus 5 | $0.00014 | $0.00249 |
| Sonnet 5 | $0.00005 | $0.00099 |
| Haiku 4.5 | $0.00003 | $0.00050 |
Grade A, and why
email-normalize-post-normalize 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 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.
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
Endpoint
POST https://requiems.xyz/v1/text/normalize
Normalize Email
Normalizes a single email address and returns the canonical form together with a breakdown of all transformations applied.
Parameters
| Name | Type | Required | Location | Description |
|---|---|---|---|---|
email |
string | yes | body | The email address to normalize. Must be a syntactically valid address. |
Request Example
{
"email": "[email protected]"
}
Response Example
{
"data": {
"original": "[email protected]",
"normalized": "[email protected]",
"local": "testuser",
"domain": "gmail.com",
"changes": [
"lowercased",
"removed_dots",
"removed_plus_tag",
"canonicalised_domain"
]
},
"metadata": {
"timestamp": "2026-01-01T00:00:00Z"
}
}
Response Fields
| Field | Type | Description |
|---|---|---|
original |
string | The email address exactly as supplied in the request body |
normalized |
string | The canonical form of the address after all transformations |
local |
string | The local part (before @) of the normalized address |
domain |
string | The domain part (after @) of the normalized address |
changes |
array | Ordered list of transformations applied. Possible values: lowercased, trimmed_whitespace, removed_dots, removed_plus_tag, canonicalised_domain. Empty array when no changes were needed. |
Errors
422validation_failed — The email field is missing or not a valid email address format.400bad_request — The request body is missing, not valid JSON, or contains unknown fields.500internal_error — Unexpected server error.
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 · 69 lines · 27 tokens per session scan A c84f2c63f847
email-normalize-post-normalize is a skill published in the GitHub repository bobadilla-tech/requiems-api-skills (2 stars, last pushed yesterday), licensed MIT. It adds 27 tokens to every session and 497 once invoked, about $0.0001 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-31.
Other skills, from other repositories
agent-ready-auth-md
Sub-skill: Implement Auth.md for agent registration discovery. Serve /auth.md with OAuth metadata at /.well-known/oauth-protected-resource and authorization server endpoints.
agent-ready-dns-aid
Sub-skill: Implement DNS-AID records so agents discover endpoints through DNS. Use SVCB/HTTPS records under agents namespace with alpn and connection parameters.
agent-ready-link-headers
Sub-skill de agent-ready-cloudflare: Implement Link Response Headers.
agent-ready-markdown-negotiation
Sub-skill de agent-ready-cloudflare: Implement Markdown Content Negotiation.
agent-ready-oauth-discovery
Sub-skill de agent-ready-cloudflare: Implement OAuth/OIDC Discovery.
agent-ready-oauth-protected-resource
Sub-skill de agent-ready-cloudflare: Implement OAuth Protected Resource Metadata.