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/flow-release)<a href="https://agentmods.dev/commands/rohitg00/awesome-claude-code-toolkit/flow-release"><img src="https://agentmods.dev/badge/commands/rohitg00/awesome-claude-code-toolkit/flow-release/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/flow-release"><img src="https://agentmods.dev/badge/commands/rohitg00/awesome-claude-code-toolkit/flow-release.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.00371 |
| Opus 5.5 | $0.00000 | $0.00148 |
| Sonnet 5.5 | $0.00000 | $0.00074 |
| Haiku 4.5 | $0.00000 | $0.00037 |
Grade A, and why
flow-release 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
Complete a feature/bugfix/hotfix flow by merging back to the target branch.
Steps
- Detect the current branch type from the prefix (feature/, bugfix/, hotfix/).
- Run pre-merge checks:
- All tests pass.
- No merge conflicts with the target branch.
- Branch is up to date with the target.
- Determine the merge target:
- feature/bugfix: merge to
developormain. - hotfix: merge to both
mainanddevelop.
- feature/bugfix: merge to
- Create a pull request if one does not exist:
gh pr create --base <target> --title "<type>: <description>".
- If auto-merge is requested:
- Rebase on target:
git rebase origin/<target>. - Merge with no-ff:
git merge --no-ff <branch>. - Tag if hotfix:
git tag -a v<version> -m "Hotfix: <description>".
- Rebase on target:
- Clean up: delete the feature branch locally and remotely.
- For hotfix, cherry-pick to develop if not merged there.
Format
Flow completed:
Branch: <branch-name>
Merged to: <target-branch>
PR: <url>
Tag: <tag if hotfix>
Cleanup: branch deleted
Changes:
- <N> commits, <N> files changed
Rules
- Never merge without passing tests and CI checks.
- Use
--no-ffmerges to preserve branch history in the merge graph. - Tag hotfix releases immediately after merging to main.
- Ensure hotfix changes also reach the develop branch.
- Confirm before deleting branches with unmerged commits.
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 · 43 lines · 0 tokens per session scan A d51d156dd6d7
flow-release 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 371 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
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.