Awesome Claude Code Toolkit is a curated collection of extensions and configuration for Claude Code, including agents, skills, commands, plugins, hooks, rules, templates, MCP configurations, and companion apps. It is for Claude Code users who want ready-made workflows and integrations for different development tasks. The catalogue add-ons are selected components from this toolkit.
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 commands/rohitg00/awesome-claude-code-toolkit/run-e2egit clone --depth 1 https://github.com/rohitg00/awesome-claude-code-toolkitWrote 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/commands/rohitg00/awesome-claude-code-toolkit/run-e2e)<a href="https://agentmods.dev/commands/rohitg00/awesome-claude-code-toolkit/run-e2e"><img src="https://agentmods.dev/badge/commands/rohitg00/awesome-claude-code-toolkit/run-e2e.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 | $0.00000 | $0.00326 |
| Opus 5 | $0.00000 | $0.00163 |
| Sonnet 5 | $0.00000 | $0.00065 |
| Haiku 4.5 | $0.00000 | $0.00033 |
Grade A, and why
run-e2e 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 yesterday.
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
/run-e2e - Execute End-to-End Tests
Run end-to-end tests against the application using Playwright or Cypress.
Steps
- Detect the e2e framework in use (Playwright, Cypress, or Selenium) by checking package.json and config files
- Verify the test configuration file exists (playwright.config.ts, cypress.config.js, etc.)
- Check if the application server is running; if not, identify the start command
- List all e2e test files matching the pattern
**/*.e2e.{ts,js}or**/*.spec.{ts,js}in the e2e/test directory - If a specific test file or pattern is provided, filter to those tests only
- Run the test suite with verbose output and capture results
- Parse test output for pass/fail counts and timing information
- For any failing tests, extract the error message, screenshot path, and stack trace
- Present a summary table: total tests, passed, failed, skipped, duration
- If failures exist, suggest fixes based on error patterns (timeout, selector, assertion)
Rules
- Always run tests in headless mode unless the user explicitly requests headed mode
- Set a default timeout of 30 seconds per test unless configured otherwise
- Capture screenshots on failure automatically
- Do not modify test files without explicit permission
- Report flaky tests if a test passes on retry but failed initially
- Ensure the base URL matches the running application port
- Clean up any test artifacts older than 7 days
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.
- yesterday First seen · 27 lines · 0 tokens per session scan A cfde35099ad3
run-e2e is a command published in the GitHub repository rohitg00/awesome-claude-code-toolkit (2,585 stars, last pushed 3mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 326 tokens. 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-09-03.
Other commands, from other repositories
t00-playwright-test
Playwright UI 测试 — 在真实浏览器中测试本地运行的 Web App，验证登录流程、功能路径、边缘案例。PJ90 等前端项目适用。.
run-yaml-test
Execute YAML-based Playwright test cases with step library references and parameter substitution support.
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.