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 dAAAb/agent-skills --skill nadmailgit clone --depth 1 https://github.com/dAAAb/agent-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/daaab/agent-skills/nadmail)<a href="https://agentmods.dev/skills/daaab/agent-skills/nadmail"><img src="https://agentmods.dev/badge/skills/daaab/agent-skills/nadmail.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.00058 | $0.02065 |
| Opus 5 | $0.00029 | $0.01033 |
| Sonnet 5 | $0.00012 | $0.00413 |
| Haiku 4.5 | $0.00006 | $0.00206 |
Grade B, and why
NadMail scanned grade B 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 6d 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
├── private-key.enc # Encrypted private key (default, chmod 600) How it starts
The opening of the file, as written. The whole thing — 283 lines — stays where its author put it; the contents beside it link to each section on GitHub.
📬 NadMail - Email for AI Agents
Your agent can handle its own email on the Nad ecosystem. No need to bother your human.
TL;DR: Get [email protected] with your .nad domain. Sign with wallet, send instantly.
Security scan notes (why ClawHub may flag this)
This skill handles private keys (for SIWE signing) and can trigger on‑chain transactions (micro-buys / emo-buy). That is expected for NadMail, but it can look suspicious to automated scanners.
To reduce risk:
- Requires Node.js >= 18
- Prefer Option A (env var) so no key is written to disk
- Managed wallet mode stores the private key encrypted only (AES-256-GCM); plaintext storage is not supported
- Mnemonic is not shown by default (opt-in via
--show-mnemonic) and is never written to disk - Emo-buy requires explicit confirmation (or
--yes) and has a daily cap (default 0.5 MON/day)
Why NadMail?
- Autonomous registration — Sign up for services, events, newsletters without human help
- Form submissions — Your agent can receive confirmation emails directly
- No CAPTCHA — Wallet signature = proof of identity
- No passwords — Cryptographic auth only
- .nad ecosystem — Native email service for the Nad ecosystem
NadMail gives AI agents verifiable email identities:
- ✨ .nad domain holders →
[email protected] - 🔗 Others →
[email protected]or[email protected]
Environment Variables
NADMAIL_PRIVATE_KEY(required forregister.js, recommended: pass via env var)NADMAIL_PASSWORD(optional; used to decrypt~/.nadmail/private-key.encwithout prompting)NADMAIL_TOKEN(optional; overrides~/.nadmail/token.jsonforsend.js/inbox.js)NADMAIL_EMO_DAILY_CAP(optional; default0.5; max MON/day for emo-buy spending)NADMAIL_SHOW_MNEMONIC(optional; set1to print mnemonic in managed setup)
🔐 Wallet Setup (Choose One)
Option A: Environment Variable (Recommended ✅)
If you already have a wallet, just set the env var — no private key stored to file:
What ships with it
6 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.
- 6d ago First seen · 283 lines · 58 tokens per session scan B f7f57c61465f
NadMail is a skill published in the GitHub repository dAAAb/agent-skills (2 stars, last pushed 8d ago), licensed MIT. It adds 58 tokens to every session and 2,065 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it B with 1 finding (asks for root). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…