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/plugins/rohitg00/awesome-claude-code-toolkit/fix-github-issue)<a href="https://agentmods.dev/plugins/rohitg00/awesome-claude-code-toolkit/fix-github-issue"><img src="https://agentmods.dev/badge/plugins/rohitg00/awesome-claude-code-toolkit/fix-github-issue/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/plugins/rohitg00/awesome-claude-code-toolkit/fix-github-issue"><img src="https://agentmods.dev/badge/plugins/rohitg00/awesome-claude-code-toolkit/fix-github-issue.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
fix-github-issue 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
{
"name": "fix-github-issue",
"version": "1.0.0",
"description": "Auto-fix GitHub issues by analyzing issue details and implementing solutions",
"commands": ["commands/fix-issue.md"]
}
What it installs
The manifest is a name and a version. 1 command travel with it, and installing the plugin installs all of them — 0 tokens a session between them. Each is measured on its own page, and each can be installed alone.
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 · 7 lines scan A fb1b50d42fcb
fix-github-issue is a plugin published in the GitHub repository rohitg00/awesome-claude-code-toolkit (2,729 stars, last pushed 5mo ago), licensed Apache-2.0. Its token cost is not measured: this kind of file is read by the harness, not the model. 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 plugins, from other repositories
knowledge-virtuoso
18 knowledge skills: design patterns, refactoring, SOLID, debugging, clean architecture, testing, API design, security, agent security, context engineering, docs lookup, scrum, performance, microservices, CI/CD, accessibility, database design, and motion design.
playbooks-virtuoso
12 playbook skills: ticket delivery, spec-driven development, TDD, branch finishing, PR feedback, handoff, worktree ops, hooks and guardrails, game feature loop, video production, security research, and retro.
code-history
Trace the git history of specific code — when a function, pattern, or file was added, modified, or removed, and the intent behind each change. Use when the user asks when or why a piece of code changed, wants the evolution of a function, or needs the commit or PR that introduced a behavior. Read-only; not for plain…
heal
A maintenance workflow for diagnosing failures and criticism, fixing their underlying causes, and reducing the chance that they happen again.
shazam
A Claude Code plugin for planning, architecture, bug triage, and development workflows. Just shout SHAZAM!
humanizer
Rewrite AI-sounding text so it reads like the writer without changing what it says.