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/write-changelog)<a href="https://agentmods.dev/commands/rohitg00/awesome-claude-code-toolkit/write-changelog"><img src="https://agentmods.dev/badge/commands/rohitg00/awesome-claude-code-toolkit/write-changelog/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/write-changelog"><img src="https://agentmods.dev/badge/commands/rohitg00/awesome-claude-code-toolkit/write-changelog.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.00293 |
| Opus 5.5 | $0.00000 | $0.00117 |
| Sonnet 5.5 | $0.00000 | $0.00059 |
| Haiku 4.5 | $0.00000 | $0.00029 |
Grade A, and why
write-changelog 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
/write-changelog - Write Changelog
Generate a detailed changelog entry from git history and merged PRs.
Steps
- Determine the version range: from the last release tag to HEAD
- Fetch all commits in the range with their messages and authors
- Fetch merged pull requests in the range using the git hosting API
- Classify changes into categories: Added, Changed, Deprecated, Removed, Fixed, Security
- Parse conventional commit prefixes (feat, fix, chore, docs, refactor, perf, test)
- Extract breaking changes from commit messages and PR descriptions
- Group changes by category and sort by significance
- Write clear, user-facing descriptions for each change (not raw commit messages)
- Include PR numbers and links for traceability
- Credit contributors with their names or usernames
- Add the date and version number to the changelog entry
- Prepend the new entry to CHANGELOG.md following Keep a Changelog format
Rules
- Follow the Keep a Changelog format (keepachangelog.com)
- Write descriptions from the user's perspective, not the developer's
- Highlight breaking changes prominently at the top of the entry
- Do not include internal refactoring unless it affects the public API
- Combine related commits into single changelog entries
- Include migration instructions for breaking changes
- Keep entries concise: one line per change with PR link
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 · 29 lines · 0 tokens per session scan A 5d1c7993989a
write-changelog 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 costs nothing until one of its globs matches a file; then it loads 293 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-08-30.
Other commands, from other repositories
create-release-note
Generate comprehensive release documentation from recent commits, producing two distinct outputs: a customer-facing release note and a technical engineering note.
ship
A command that runs several specialist checks before software is released, then combines their findings into a decision about whether to launch.
commit
Smart conventional commit with security validation, branch flow enforcement, and auto-detection. Use for git commit, commit changes, save work, stage and commit.
adk-ts-changelog
Generate changelog entries and community release notes for ADK-TS from git history and changesets.
release-impact
Analyze the blast radius of a change before release — what else might break or be affected.
dd-done
Mark changes as done, merge RC to official documents.