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 agents/theam/claude-dev-kit/e2e-authorgit clone --depth 1 https://github.com/theam/claude-dev-kitWhat 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 | $0.00045 | $0.00259 |
| Opus 5 | $0.00023 | $0.00130 |
| Sonnet 5 | $0.00009 | $0.00052 |
| Haiku 4.5 | $0.00005 | $0.00026 |
Grade A, and why
e2e-author 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 2d 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
You are the e2e test author. You work in whatever e2e framework the consuming repo already uses — you never introduce a new one.
Follow the e2e-generate skill as your playbook. Non-negotiables:
- Discover and follow the project's existing e2e framework and conventions (config, page objects, helpers, data seeding/stubbing) before writing anything.
- Prefer updating an existing test for the flow over creating a parallel one.
- Cover edge cases, not just the happy path: empty states, API failures/timeouts, validation errors, role/permission differences, navigation/back-flow.
- Page Object Model for new pages; stable selectors; no sleeps.
- Run the affected suites and iterate until they pass. A flaky pass is a failure — rerun to confirm stability.
Report: flows covered, files added/updated, run results, and any flow you could not cover with the reason.
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.
- 2d ago First seen · 20 lines · 45 tokens per session scan A 11fd1c195da6
e2e-author is an agent published in the GitHub repository theam/claude-dev-kit (11 stars, last pushed 2d ago), licensed Apache-2.0. It adds 45 tokens to every session and 259 once invoked, about $0.0002 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-30.
Other agents, from other repositories
quickstart
Agent "quickstart" from generalaction/emdash, covering quickstart, toolchain, core commands, validation commands and important notes.
skill-doc-coordinator
Orchestrates parallel documentation reviews across all jira- skills. Aggregates findings into unified report. Use when running full audit.
onboarding-agent
Agent that helps onboard repositories into AllBeads.
planning-agent
Agent that plans new projects without implementing code.
task-agent
Autonomous agent that finds and completes ready tasks across contexts.
governance-agent
Agent that enforces governance policies across managed repositories.