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.
git 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/record-test)<a href="https://agentmods.dev/commands/rohitg00/awesome-claude-code-toolkit/record-test"><img src="https://agentmods.dev/badge/commands/rohitg00/awesome-claude-code-toolkit/record-test/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/commands/rohitg00/awesome-claude-code-toolkit/record-test"><img src="https://agentmods.dev/badge/commands/rohitg00/awesome-claude-code-toolkit/record-test.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.00000 | $0.00292 |
| Opus 5.5 | $0.00000 | $0.00117 |
| Sonnet 5.5 | $0.00000 | $0.00058 |
| Haiku 4.5 | $0.00000 | $0.00029 |
Grade A, and why
record-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 1mo 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
/record-test - Record New E2E Test
Record user interactions to generate an end-to-end test file.
Steps
- Ask the user for the test name and the user flow to record (e.g., "login flow", "checkout process")
- Determine the e2e framework in use from the project configuration
- Identify the base URL and starting page for the recording session
- For Playwright: use
npx playwright codegenwith the target URL - For Cypress: set up Cypress Studio or guide manual recording
- Capture the generated test code from the recording session
- Clean up the recorded code: add proper assertions, remove redundant waits
- Add descriptive test names and group related interactions into logical steps
- Add page object references if the project uses the Page Object Model pattern
- Save the test file to the appropriate directory with the correct naming convention
- Run the newly created test to verify it passes
- Report the result and suggest additional assertions to strengthen the test
Rules
- Follow the project's existing test naming conventions
- Use data-testid selectors over CSS selectors when available
- Add at least one assertion per user interaction step
- Include setup and teardown hooks if the test requires authentication
- Do not hardcode test data; use fixtures or environment variables
- Keep recorded tests under 50 lines; split longer flows into separate tests
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.
- 1mo ago First seen · 28 lines · 0 tokens per session scan A 11af13fd0f34
record-test is a command published in the GitHub repository rohitg00/awesome-claude-code-toolkit (2,721 stars, last pushed 5mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 292 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
vios-dev-sanity
Execute VIOS/VST sanity test cases from the viosdevsanity.xlsx spreadsheet against a running VIOS web UI instance using Playwright. Tests are loaded dynamically from the xlsx — no hardcoded test matrix.
t00-playwright-test
A command for testing a locally running web app in a real browser with Playwright, a browser automation and testing tool. It checks normal user flows and selected edge cases, then reports results with screenshots.
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.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.