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 EthanYoQ/Skill-hub --skill email-batch-testgit clone --depth 1 https://github.com/EthanYoQ/Skill-hubWrote 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/ethanyoq/skill-hub/email-batch-test)<a href="https://agentmods.dev/skills/ethanyoq/skill-hub/email-batch-test"><img src="https://agentmods.dev/badge/skills/ethanyoq/skill-hub/email-batch-test/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/ethanyoq/skill-hub/email-batch-test"><img src="https://agentmods.dev/badge/skills/ethanyoq/skill-hub/email-batch-test.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.00039 | $0.00347 |
| Opus 5.5 | $0.00016 | $0.00139 |
| Sonnet 5.5 | $0.00008 | $0.00069 |
| Haiku 4.5 | $0.00004 | $0.00035 |
Grade A, and why
email-batch-test 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 1mo 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 Batch Test
Current Authority
Read AGENTS.md, then read both files under references/.
The canonical QQ full-range truth manifest is:
test_dataset/qq_20251125_20260614_rebuilt_20260614_1035/truth_manifest.json
Its required contract is:
included_count = 215pending_review_count = 0finalized = true- date range
2025-11-25through2026-06-14
Do not substitute an older manifest or describe a non-final truth set as authoritative.
Required Gate
- Build the Windows package from the exact candidate revision.
- Create a fresh child of
manual_frontend_runsand clear only its output-scoped state. - Preserve
%APPDATA%\InvoiceFlowAI\user_settings.jsonand its encrypted credentials. - Launch the packaged EXE visibly through
scripts/frontend_truth_acceptance.py. - Require finalized run evidence and a fresh
batch_validation.pyaudit. - Accept only an explicit result with P0, P1, P2, and manual counts all zero.
No result may be reported as probable, suspected, or unconfirmed. Missing authority is a failed gate.
Secondary Mailboxes
Run another mailbox only when its local manifest is present, finalized, has zero pending review, and the task explicitly requires that scope. Never depend on a stale or missing worktree path.
What ships with it
2 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.
- 1mo ago Changed · +5 lines · -42 tokens per session e177b43b0fbe
- 1mo ago First seen · 34 lines · 81 tokens per session scan A bf481a7e0f7d
email-batch-test is a skill published in the GitHub repository EthanYoQ/Skill-hub (11 stars, last pushed yesterday), licensed MIT. It adds 39 tokens to every session and 347 once invoked, about $0.0002 per session on Opus 5.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
qa
Browser-based QA verification. Launches a real browser, navigates the app, clicks buttons, fills forms, and tests user flows. Works as a standalone skill or as a phase end condition in campaigns. Requires Playwright (optional dependency, graceful skip if not installed).
live-preview
Mid-build visual verification loop. Takes screenshots of components during construction, not just after. Catches visual regressions and invisible features before they compound. Requires Playwright or similar screenshot tool.
test-gen
Generate and verify tests — happy path, edge cases, error paths — using the project's own framework and patterns.
verify
Self-test the Citadel hook pipeline from within a live session. Exercises real tool calls (Write, Edit, Bash, Read) and checks that hooks fired, telemetry accumulated, and no errors occurred. Reports HOOK HEALTH: PASS or HOOK HEALTH: FAIL with a per-hook breakdown.
wakeflow-test
Use in a window that has received a Wakeflow delivery for a test target - read the frozen test contract in the task package, run its approved steps in the real environment against the landing the implementation produced, record what each step actually observed with its evidence, then import the per-step report and…
quality-assurance-engineer
QA Engineer / Quality Assurance role skill. Use when you need to write test cases, analyse defects, evaluate acceptance criteria, design test strategies, assess release quality, or validate the quality of a feature implementation. Keywords: test cases, defect tracking, quality assurance, acceptance testing, boundary…