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/generate-changelog)<a href="https://agentmods.dev/commands/rohitg00/awesome-claude-code-toolkit/generate-changelog"><img src="https://agentmods.dev/badge/commands/rohitg00/awesome-claude-code-toolkit/generate-changelog.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.00019 | $0.00445 |
| Opus 5 | $0.00010 | $0.00222 |
| Sonnet 5 | $0.00004 | $0.00089 |
| Haiku 4.5 | $0.00002 | $0.00044 |
Grade A, and why
generate-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 8d 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
Generate a changelog from git history, grouping commits by type and version.
Steps
- Determine the version range:
- If
--fromand--toare specified, use those tags. - Otherwise, generate from the last tag to HEAD.
- For initial changelog, process all commits.
- If
- Parse commits using conventional commit format:
feat: Features section.fix: Bug Fixes section.perf: Performance section.docs: Documentation section.refactor: Code Refactoring section.test: Tests section.chore/ci/build: Maintenance section.BREAKING CHANGE: Breaking Changes section (always first).
- For each entry, include:
- Commit subject line.
- Scope in parentheses if present.
- PR number or commit hash as reference.
- Author attribution.
- Sort sections by importance: Breaking > Features > Fixes > Performance > Others.
- Write or update
CHANGELOG.mdwith the new version at the top. - If existing
CHANGELOG.mdexists, prepend the new version section.
Format
# Changelog
## [1.2.0] - 2026-02-04
### Breaking Changes
- **api**: Removed deprecated `/v1/users` endpoint (#123)
### Features
- **auth**: Add OAuth2 PKCE flow support (#120)
### Bug Fixes
- **db**: Fix connection pool leak under high concurrency (#118)
### Performance
- **cache**: Reduce Redis round-trips by 40% with pipelining (#115)
Rules
- Follow Keep a Changelog format (keepachangelog.com).
- Always include the date in each version header.
- Group by type, then sort by scope within each group.
- Skip merge commits and CI-only changes.
- Link version headers to git comparison URLs when possible.
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.
- 8d ago First seen · 59 lines · 19 tokens per session scan A b11a9059a85b
generate-changelog is a command published in the GitHub repository rohitg00/awesome-claude-code-toolkit (2,595 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 19 tokens to every session and 445 once invoked, about $0.0001 per session on Opus 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-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.
commit
Smart conventional commit with security validation, branch flow enforcement, and auto-detection. Use for git commit, commit changes, save work, stage and commit.
ship
A command that runs several specialist checks before software is released, then combines their findings into a decision about whether to launch.
t00-publish
A release-preparation command that copies a project into a GitHub staging folder and checks which files are safe to publish.
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.