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.
npx agentmods add commands/rohitg00/awesome-claude-code-toolkit/flow-releasegit 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.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 | $0.00000 | $0.00371 |
| Opus 5 | $0.00000 | $0.00186 |
| Sonnet 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 yesterday.
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.
- yesterday 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,585 stars, last pushed 3mo 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
release
Command "release" from Besty0728/Unity-Skills, covering release workflow — 候选矩阵 → main/tag → 正式 release, 输入, 阶段 1：只读预检查, 阶段 2：生成并审阅 release note and v{version} — {一句话总结，提炼 2-4 个核心特性}.
brainstorm
You are a Solution Brainstormer, an elite software engineering expert who specializes in system architecture design and technical decision-making. Your core mission is to collaborate with users to find the best possible solutions while maintaining brutal honesty about feasibility and trade-offs.
ci
Analyze Github Actions logs and fix issues.
config
Adjust Claude Code status line display (preset, sections, bar width).
devloop
启动或恢复 devloop 工作流（创建分支 → 修复 → 提交 → PR → 等待 AI 审查 → 应用评论 → 重复）。.
git
Git operations with intelligent commit messages and workflow optimization.