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-load-testgit 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-load-test)<a href="https://agentmods.dev/commands/rohitg00/awesome-claude-code-toolkit/run-load-test"><img src="https://agentmods.dev/badge/commands/rohitg00/awesome-claude-code-toolkit/run-load-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 | $0.00000 | $0.00312 |
| Opus 5 | $0.00000 | $0.00156 |
| Sonnet 5 | $0.00000 | $0.00062 |
| Haiku 4.5 | $0.00000 | $0.00031 |
Grade A, and why
run-load-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 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-load-test - Execute Load Test
Run load and stress tests against API endpoints or web pages.
Steps
- Ask the user for the target URL or endpoint to test
- Determine load testing parameters: concurrent users (default 50), duration (default 60s), ramp-up period (default 10s)
- Check if a load testing tool is installed (k6, Artillery, or autocannon); recommend k6 if none found
- Create or locate the load test script for the target endpoint
- Configure request headers, authentication tokens, and payload if needed
- Execute the load test with the specified parameters
- Monitor real-time metrics: requests/sec, latency percentiles (p50, p95, p99), error rate
- Capture the full results including response time distribution
- Identify performance bottlenecks: slow endpoints, high error rates, timeout patterns
- Present results in a formatted table with pass/fail thresholds
- Save the results to a timestamped report file
Rules
- Never run load tests against production without explicit user confirmation
- Default to a conservative load profile (50 VUs, 60s duration) unless specified
- Always include a ramp-up period to avoid sudden spikes
- Monitor system resources if testing locally (CPU, memory)
- Stop the test immediately if error rate exceeds 50%
- Include response time percentiles, not just averages
- Warn if the target appears to be a third-party service
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 · 28 lines · 0 tokens per session scan A bcff6c819010
run-load-test is a command published in the GitHub repository rohitg00/awesome-claude-code-toolkit (2,587 stars, last pushed 3mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 312 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
ui-test
Run VIOS UI tests using the playwright plugin.
brainstorm
You are a Solution Brainstormer, an elite software engineering expert who specializes in system architecture design and technical decision-making. Your core mission is to collaborate with users to find the best possible solutions while maintaining brutal honesty about feasibility and trade-offs.
t00-playwright-test
Playwright UI 测试 — 在真实浏览器中测试本地运行的 Web App，验证登录流程、功能路径、边缘案例。PJ90 等前端项目适用。.
config
Adjust Claude Code status line display (preset, sections, bar width).
ci
Analyze Github Actions logs and fix issues.
checklist
Generate a custom checklist for the current feature based on user requirements.