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/fix-issues)<a href="https://agentmods.dev/commands/rohitg00/awesome-claude-code-toolkit/fix-issues"><img src="https://agentmods.dev/badge/commands/rohitg00/awesome-claude-code-toolkit/fix-issues.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.1 | $0.00000 | $0.00314 |
| Opus 5 | $0.00000 | $0.00157 |
| Sonnet 5 | $0.00000 | $0.00063 |
| Haiku 4.5 | $0.00000 | $0.00031 |
Grade A, and why
fix-issues 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
/fix-issues - Fix Lighthouse Issues
Apply fixes for Lighthouse audit failures to improve scores.
Steps
- Load the most recent Lighthouse audit results
- Prioritize issues by impact: high-impact, medium-impact, low-impact
- For Performance issues:
- Add lazy loading to below-the-fold images
- Optimize image formats and sizes (WebP, AVIF)
- Add preload hints for critical resources
- Defer non-critical JavaScript and CSS
- For Accessibility issues:
- Add missing alt text to images
- Fix color contrast ratios
- Add ARIA labels to interactive elements
- Ensure proper heading hierarchy
- For Best Practices issues:
- Fix mixed content (HTTP resources on HTTPS pages)
- Add security headers (CSP, X-Frame-Options)
- Update deprecated APIs
- For SEO issues:
- Add missing meta descriptions and titles
- Fix mobile viewport configuration
- Add structured data markup
- Apply each fix incrementally and verify it resolves the flagged audit
- Re-run Lighthouse to measure the improvement
- Report: fixes applied, score changes, remaining issues
Rules
- Fix high-impact issues first for maximum score improvement
- Do not break existing functionality while fixing audit issues
- Test visual appearance after applying performance optimizations
- Verify accessibility fixes with manual keyboard navigation
- Keep performance optimizations progressive (do not block rendering)
- Document each fix for team awareness and future maintenance
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 · 39 lines · 0 tokens per session scan A 1d77be4c3cfa
fix-issues 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 314 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
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.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.