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 petrkindlmann/qa-skills --skill email-testinggit clone --depth 1 https://github.com/petrkindlmann/qa-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/petrkindlmann/qa-skills/email-testing)<a href="https://agentmods.dev/skills/petrkindlmann/qa-skills/email-testing"><img src="https://agentmods.dev/badge/skills/petrkindlmann/qa-skills/email-testing/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/petrkindlmann/qa-skills/email-testing"><img src="https://agentmods.dev/badge/skills/petrkindlmann/qa-skills/email-testing.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Socket pass
- Snyk warn
- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 166 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00251 | $0.04890 |
| Opus 5.5 | $0.00100 | $0.01956 |
| Sonnet 5.5 | $0.00050 | $0.00978 |
| Haiku 4.5 | $0.00025 | $0.00489 |
Grade A, and why
email-testing 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 3d 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.
- **Capture is wired:** `curl -s localhost:8025/api/v1/messages | jq '.total'` returns a How it starts
The opening of the file, as written. The whole thing — 361 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Quick Route
| Situation | Go to |
|---|---|
| Pick a capture tool | "Capture-inbox decision tree" below |
| Poll an inbox without a sleep | references/mailpit-playwright.md (polling helper) |
| Pull an OTP / link out of the body | references/mailpit-playwright.md (extraction) |
| Full password-reset / signup / magic-link E2E | references/mailpit-playwright.md |
| Real addresses on staging | references/hosted-inboxes.md (Mailosaur) |
| Per-test throwaway inbox | references/hosted-inboxes.md (MailSlurp / ShazaMail) |
| Just preview a template locally | references/hosted-inboxes.md (Ethereal) |
| Flag SPF/DKIM/DMARC problems | references/deliverability.md |
| Tests pass locally, "no email yet" in CI | "Flaky email in CI" below |
Discovery Questions
Check .agents/qa-project-context.md first — if it exists, use it and skip anything
answered there.
- Where does the email need to be received? Local capture (Mailpit) covers most functional flows for free. A real, externally-deliverable address (staging, a third- party ESP, real DNS) means a hosted inbox (Mailosaur / MailSlurp). This is the single biggest tool-selection driver.
- How parallel is the suite? High parallelism makes "the latest email" ambiguous — you need per-test unique addresses or per-test inboxes, not a shared mailbox.
- Which flows? Signup confirmation, password reset, magic-link login, OTP/MFA, notification emails — they share one shape (capture, extract, complete) but differ in what you extract (link vs 6-digit code).
- Is deliverability in scope? "Lands in inbox / passes SPF, DKIM, DMARC" is a separate non-blocking suite, not part of the functional OTP test. Decide upfront.
- Local-only preview, or CI assertions? Previewing a template during dev is Ethereal; asserting in CI is Mailpit/Mailosaur/MailSlurp/ShazaMail. Don't confuse the two.
What ships with it
3 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.
- 3d ago Changed · +1 lines b331009a6811
- 4d ago Changed · +3 lines · +9 tokens per session 3dbdf365f361
- 5d ago Changed · +8 lines · +1 tokens per session 7f3dc5e83a30
- 1mo ago First seen · 349 lines · 241 tokens per session scan A 698f97f4684e
email-testing is a skill published in the GitHub repository petrkindlmann/qa-skills (210 stars, last pushed 3d ago), licensed MIT. It adds 251 tokens to every session and 4,890 once invoked, about $0.0010 per session on Opus 5.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 skills, from other repositories
Checkly Monitoring as Code
Teach agents to build synthetic monitoring as code with Checkly, including Playwright browser checks, API checks, alerting, and CI deploy workflows.
CI Test Sharding Parallelization
Teach agents to shard and parallelize Playwright, Jest, and pytest suites in CI to reduce wall-clock time while merging reports reliably.
CI/CD Pipeline Config
CI/CD pipeline configuration skill for test automation, covering GitHub Actions, Jenkins, GitLab CI, test parallelization, reporting, and artifact management.
Ephemeral Environment Testing
Testing in ephemeral preview environments for pull requests including environment provisioning, data seeding, and automated teardown.
Desktop Application Testing
Testing desktop applications built with Electron, Tauri, or native frameworks including window management, IPC, tray icons, and auto-update testing.
Azure Microsoft Playwright Testing Ts
Run Playwright tests at scale using Azure Playwright Workspaces (formerly Microsoft Playwright Testing). Use when scaling browser tests across cloud-hosted browsers, integrating with CI/CD pipeline...