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 agentmods add skills/ethanyoq/skill-hub/email-batch-testnpx 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.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.00081 | $0.00389 |
| Opus 5 | $0.00041 | $0.00195 |
| Sonnet 5 | $0.00016 | $0.00078 |
| Haiku 4.5 | $0.00008 | $0.00039 |
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 5d 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
跑批测试 Skill
触发条件
当任务涉及以下关键词时自动触发：
- 跑批、batch test、批量测试
- 真值审计、truth audit
- 回归验证、regression
- P0、P1、P2
必读文件
- 项目根目录
CLAUDE.md— 了解 FROZEN/GUARDED/SAFE 区域定义 references/test-standards.md— P0/P1/P2 量化标准references/regression-gate.md— 双邮箱回归门禁流程
核心规则
- 跑批前：确认使用哪个邮箱的真值集
- 跑批后：必须运行
strict_truth_audit.py对比真值 - 修改代码后：检查改动是否触碰 FROZEN/GUARDED ZONE
- 触碰保护区域：必须同时跑 QQ + 163 真值集验证
- 提交前：P0 必须 = 0
真值集位置
- QQ：
test_dataset/qq_20260201_20260311_final/truth_manifest.json - 163：
.claude/worktrees/test-163-batch/test_dataset/163_20260301_20260319/truth_manifest.json
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.
- 5d 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 (9 stars, last pushed 2d ago), licensed MIT. It adds 81 tokens to every session and 389 once invoked, about $0.0004 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
watch
File sentinel that monitors the working directory for changes and marker comments, then auto-triggers appropriate skills. Poll-based via git diff against the last scan commit. Writes intake items for batch processing and routes marker actions through /do. Use for automatic reactions to file changes; do NOT use for…
pr-watch
Local PR watcher. Monitors CI status, automatically fixes failing checks by reading failure logs and applying targeted fixes, then optionally merges when all checks pass. Local CLI analog to Claude Code's cloud auto-fix feature.
review
5-pass structured code review — correctness, security, performance, readability, consistency.
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.
marshal
Meta-orchestrator that takes any direction — broad, specific, or vague — and autonomously chains skills and context into actionable work. Gathers context from codebase, docs, and memory. Only asks the user when it genuinely cannot proceed. Single-session orchestrator.
systematic-debugging
4-phase root cause analysis: observe, hypothesize, verify, fix. Enforces investigation before any code changes. Emergency stop after 2 failed fixes. Prevents shotgun debugging and fix cascades.