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/find-leaks)<a href="https://agentmods.dev/commands/rohitg00/awesome-claude-code-toolkit/find-leaks"><img src="https://agentmods.dev/badge/commands/rohitg00/awesome-claude-code-toolkit/find-leaks/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/find-leaks"><img src="https://agentmods.dev/badge/commands/rohitg00/awesome-claude-code-toolkit/find-leaks.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.00324 |
| Opus 5 | $0.00000 | $0.00162 |
| Sonnet 5 | $0.00000 | $0.00065 |
| Haiku 4.5 | $0.00000 | $0.00032 |
Grade A, and why
find-leaks 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 5d 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
/find-leaks - Find Memory Leaks
Detect and diagnose memory leaks in the application.
Steps
- Configure the application for leak detection with appropriate tooling
- Establish a baseline memory measurement at application startup
- Run a repetitive workload: process N requests, render N times, or execute N iterations
- Measure memory after each iteration to detect steady growth
- Force garbage collection between measurements to isolate true leaks
- Identify objects that grow in count across iterations without being released
- Trace the retention path: what is holding references to leaked objects
- Check common leak sources:
- Event listeners not removed on cleanup
- Closures capturing large scopes
- Growing caches without eviction
- Circular references preventing GC
- Timers and intervals not cleared
- For each leak, identify the source file, line, and the allocation site
- Suggest specific fixes: removeEventListener, WeakRef, cache size limits
- Verify the fix by re-running the leak detection scenario
- Report: leaks found, estimated memory impact, fix suggestions
Rules
- Run leak detection for at least 100 iterations to confirm a pattern
- Distinguish between expected memory growth and actual leaks
- Check both heap memory and native memory (buffers, file handles)
- Verify leaks are reproducible before reporting
- Consider the application lifecycle; some growth is expected during warmup
- Check for connection pool leaks (database, HTTP, WebSocket)
- Report the growth rate (bytes per iteration) for each detected leak
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.
- 5d ago First seen · 34 lines · 0 tokens per session scan A 0ccd33bc2bf6
find-leaks is a command published in the GitHub repository rohitg00/awesome-claude-code-toolkit (2,598 stars, last pushed 3mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 324 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
debug
Apply expert debugging methodology to investigate a specific issue.
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.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.