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 theam/claude-dev-kit --skill e2e-generategit clone --depth 1 https://github.com/theam/claude-dev-kitWrote 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/theam/claude-dev-kit/e2e-generate)<a href="https://agentmods.dev/skills/theam/claude-dev-kit/e2e-generate"><img src="https://agentmods.dev/badge/skills/theam/claude-dev-kit/e2e-generate/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/theam/claude-dev-kit/e2e-generate"><img src="https://agentmods.dev/badge/skills/theam/claude-dev-kit/e2e-generate.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.00052 | $0.00701 |
| Opus 5.5 | $0.00021 | $0.00280 |
| Sonnet 5.5 | $0.00010 | $0.00140 |
| Haiku 4.5 | $0.00005 | $0.00070 |
Grade A, and why
e2e-generate 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 2mo 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.
How it starts
The opening of the file, as written. The whole thing — 36 lines — stays where its author put it; the contents beside it link to each section on GitHub.
E2E Test Generation
When a user story changes user-facing behavior and the project already does e2e, an existing e2e test must be updated or a new one created before the story is done. This skill is framework-agnostic — it uses whatever e2e stack the consuming repo already has, and never introduces a new one unprompted.
Adaptive gate (see instructions/testing-standards.md): if the repo has no e2e setup, this is a recommendation, not a blocker — report "no e2e setup; recommend adding one" (and offer to, if the user wants), and do not scaffold a framework. Only treat missing e2e as a hard failure when gates.e2e is required in .claude/dev-kit.json.
Process
- Identify the affected flow(s) from the story's acceptance criteria and the diff: which pages, routes, forms, and roles are involved.
- Discover the project's e2e framework and conventions first — before writing anything. If
.claude/dev-kit.jsonnames a stack,instructions/stacks/<id>.mdlists the frameworks common for it as a starting hint. Then look for the config and test tree of whatever the repo actually uses (e.g.playwright.config.*+e2e/,cypress.config.*+cypress/, a Selenium/WebDriver test project,*.featurefiles for Cucumber, etc.) and reuse its existing page objects, fixtures, helpers, and app/API seeding or stubbing. Follow them exactly; do not introduce a new pattern or framework when one exists. If the repo has no e2e setup at all, say so and propose one that fits the stack instead of scaffolding silently. - Prefer updating an existing test for the flow over creating a parallel one.
- Write the scenarios. Every generated suite must cover realistic edge cases, not just the happy path:
- Empty states
- API failures and timeouts
- Validation errors
- Role/permission differences where applicable
- Navigation and back-flow behavior where applicable
- Run the tests with the project's e2e command (check the consuming repo's CLAUDE.md; e.g.
npx playwright test <file>,npx cypress run, or the repo's WebDriver test command). Related e2e tests must pass before PR creation.
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.
- 2mo ago First seen · 36 lines · 52 tokens per session scan A 448a47c51f45
e2e-generate is a skill published in the GitHub repository theam/claude-dev-kit (16 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 52 tokens to every session and 701 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-30.
Other skills, from other repositories
api-audit
API and endpoint integrity audit across 10 dimensions (D1-D10) plus optional contract stability (D11) and optional OWASP API Security Top 10 (D12: BOLA/BOPLA/BFLA, mass assignment, JWT alg-confusion, GraphQL introspection). Covers validation, payloads, pagination, errors, caching, HTTP semantics, waterfalls, rate…
api-testing
Verify API contracts against a real controlled service. Triggers on "test API", "API 测试".
flask-quality
A quality-check workflow for Flask applications, a Python web framework. It runs tests, strict type checks, and code-formatting checks.
run
The single lifecycle entry point — take one or more tickets and drive each through its whole lifecycle (investigate, red tests, implement, gates, review, PR, merge, archive), interleaving them. Lean by default — one worker per ticket runs red tests, implementation and the gate scripts in one worktree, then…
brooks-sweep
Full-sweep mode: runs a unified analysis across all quality dimensions — code decay, architecture, tech debt, and test quality — then applies fixes directly to the codebase. Safe changes are auto-applied; risky changes are confirmed before execution. Drawing on twelve classic engineering books. Triggers when: user…
brooks-test
Test quality review drawing on twelve classic engineering books — with primary focus on xUnit Test Patterns, The Art of Unit Testing, How Google Tests Software, and Working Effectively with Legacy Code — that diagnoses structural problems in an existing test suite: brittleness, mock abuse, coverage illusions, slow…