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/edmonds-commerce-limited/claude-code-hooks-daemon/acceptance-testnpx skills add Edmonds-Commerce-Limited/claude-code-hooks-daemon --skill acceptance-testgit clone --depth 1 https://github.com/Edmonds-Commerce-Limited/claude-code-hooks-daemonWrote 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/edmonds-commerce-limited/claude-code-hooks-daemon/acceptance-test)<a href="https://agentmods.dev/skills/edmonds-commerce-limited/claude-code-hooks-daemon/acceptance-test"><img src="https://agentmods.dev/badge/skills/edmonds-commerce-limited/claude-code-hooks-daemon/acceptance-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.00019 | $0.01657 |
| Opus 5 | $0.00010 | $0.00829 |
| Sonnet 5 | $0.00004 | $0.00331 |
| Haiku 4.5 | $0.00002 | $0.00166 |
Grade D, and why
acceptance-test scanned grade D with 2 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 today.
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.
- Examples: git reset --hard, rm -rf, sudo pip, sed -i Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
- Examples: git reset --hard, rm -rf, sudo pip, sed -i How it starts
The opening of the file, as written. The whole thing — 220 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/acceptance-test - Acceptance Testing Skill
Run this first
Claude Code loads this markdown and nothing else — the file below is not run for you, and it holds the procedure to follow (Plan 00324):
bash "${CLAUDE_SKILL_DIR:-.claude/skills/acceptance-test}/invoke.sh" <filter, or omit for all>
Follow its output exactly; what is written here is orientation.
Description
Execute acceptance tests for hooks daemon handlers via real Claude Code tool calls in the main thread. Tests verify real-world handler behaviour by invoking actual tools (Bash, Write, Edit, Read) and observing hook responses in system-reminders.
CRITICAL: Main Thread Only
Acceptance tests MUST be executed in the main Claude Code session. Sub-agent strategies (parallel Haiku batches) are unreliable and forbidden:
- Sub-agents run out of context on large test suites
- Sub-agents cannot use Write/Edit tools (PreToolUse:Write tests fail)
- Lifecycle events (SessionStart, SessionEnd) only fire in the main session
- Advisory messages in system-reminders are only visible to the main session
- The v2.9.0 incident proved async agents create race conditions with release gates
The ONLY valid acceptance test is a real tool call in the main thread with the hook response observed directly.
Usage
# Test all handlers (default)
/acceptance-test
/acceptance-test all
# Test only blocking handlers
/acceptance-test blocking-only
# Test only advisory handlers
/acceptance-test advisory-only
# Test only context injection handlers
/acceptance-test context-only
# Test specific handler by name substring
/acceptance-test DestructiveGit
/acceptance-test npm
Parameters
- filter (optional): Test filter
all(default): Run all testsblocking-only: Only blocking handlers (test_type=blocking)advisory-only: Only advisory handlers (test_type=advisory)context-only: Only context injection handlers (test_type=context)<handler-substring>: Filter by handler name (e.g., "Git", "npm", "TDD")
What ships with it
1 file 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.
- today Changed · +11 lines 128dde4eea60
- 5d ago First seen · 209 lines · 19 tokens per session scan D 6ff90642989d
acceptance-test is a skill published in the GitHub repository Edmonds-Commerce-Limited/claude-code-hooks-daemon (3 stars, last pushed yesterday), licensed MIT. It adds 19 tokens to every session and 1,657 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it D with 2 findings (asks for root, recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
test-native-extension
Validate a third-party control repo across four automated layers plus one printed manual recipe. Layer 1 asserts native-source structure (Android getName() and iOS +moduleName to manifest nativeModule; @ReactMethod / RCTEXPORTMETHOD to methods; no @ReactModule) plus load/init readiness (ReactPackage public no-arg…
test-site
Tests a deployed, activated Power Pages site at runtime using browser-based navigation, page crawling, and API request verification via Playwright. Use when the user wants to test, verify, or smoke-test their deployed site.
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).
better-auth
Skill for integrating Better Auth - comprehensive TypeScript authentication framework for Cloudflare D1, Next.js, Nuxt, and 15+ frameworks. Use when adding auth, encountering D1 adapter errors, or implementing OAuth/2FA/RBAC features.
recipe-add-integration-tests
Add integration/E2E tests to existing codebase using Design Docs.
aceternity-ui
100+ animated React components (Aceternity UI) for Next.js with Tailwind. Use for hero sections, parallax, 3D effects, or encountering animation, shadcn CLI integration errors.