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/triage-issues)<a href="https://agentmods.dev/commands/rohitg00/awesome-claude-code-toolkit/triage-issues"><img src="https://agentmods.dev/badge/commands/rohitg00/awesome-claude-code-toolkit/triage-issues/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/triage-issues"><img src="https://agentmods.dev/badge/commands/rohitg00/awesome-claude-code-toolkit/triage-issues.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.00017 | $0.00337 |
| Opus 5.5 | $0.00007 | $0.00135 |
| Sonnet 5.5 | $0.00003 | $0.00067 |
| Haiku 4.5 | $0.00002 | $0.00034 |
Grade A, and why
triage-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 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
/triage-issues - Triage GitHub Issues
Analyze and triage open GitHub issues for prioritization.
Steps
- Fetch all open issues from the repository using the GitHub API
- Filter issues by: unlabeled, unassigned, or stale (no activity in 30 days)
- Analyze each issue for: completeness, reproducibility, severity, and impact
- Suggest labels based on issue content: bug, feature, enhancement, documentation, question
- Assess priority based on: user impact, frequency of reports, component affected
- Identify duplicate issues by comparing titles and descriptions with existing issues
- Flag issues that need more information from the reporter
- Group related issues that could be addressed together
- Suggest assignees based on the component or area affected
- Create a triage summary: total open, by priority, by label, stale issues
- Recommend which issues to close (duplicates, won't fix, cannot reproduce)
- Generate a prioritized backlog view for the next sprint
Rules
- Do not close issues without user confirmation
- Respect existing labels and assignments; suggest changes, do not override
- Mark issues as stale only if truly inactive (no comments, no linked PRs)
- Prioritize bugs over features, security issues over all others
- Consider the number of thumbs-up reactions as a popularity signal
- Do not auto-assign issues; suggest assignees for human decision
- Keep triage notes factual and neutral in tone
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 · 34 lines · 17 tokens per session scan A e7680ec4c36d
triage-issues is a command published in the GitHub repository rohitg00/awesome-claude-code-toolkit (2,717 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 17 tokens to every session and 337 once invoked, about $0.0001 per session on Opus 5.5. 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
add-to-todos
Add todo item to TO-DOS.md with context from conversation.
create-plan
Create hierarchical project plans for solo agentic development (briefs, roadmaps, phase plans).
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.