flow-start

flow-start is a command for coding agents from rohitg00/awesome-claude-code-toolkit. It costs 0 tokens per session (340 once invoked), scanned A, original, Apache-2.0.

A command for starting a new Git feature, bug-fix, or hotfix branch using Git-flow conventions. Git-flow is a branching approach that separates ongoing development from production fixes.

In plain words
What is it for?
Use it to create and publish feature/, bugfix/, or hotfix/ branches, link them to GitHub issues, and show the next development steps.
Why use it?
It reduces errors when choosing a base branch, naming the branch, syncing with the remote repository, or accidentally working on an unclean branch.

Command

Part of the git-flow plugin — 2 commands shipped together

About the project

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.

rohitg00/awesome-claude-code-toolkit · 2,585 stars · on GitHub

Install

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.

agentmods
npx agentmods add commands/rohitg00/awesome-claude-code-toolkit/flow-start
Clone the repo
git clone --depth 1 https://github.com/rohitg00/awesome-claude-code-toolkit

Or install git-flow, the plugin that ships this one along with the rest of its 2 commands.

Wrote 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.

agentmods badge for flow-start

README.md
[![agentmods](https://agentmods.dev/badge/commands/rohitg00/awesome-claude-code-toolkit/flow-start.svg)](https://agentmods.dev/commands/rohitg00/awesome-claude-code-toolkit/flow-start)
Your own site
<a href="https://agentmods.dev/commands/rohitg00/awesome-claude-code-toolkit/flow-start"><img src="https://agentmods.dev/badge/commands/rohitg00/awesome-claude-code-toolkit/flow-start.svg" alt="Measured on agentmods" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 340 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.00340
Opus 5 $0.00000 $0.00170
Sonnet 5 $0.00000 $0.00068
Haiku 4.5 $0.00000 $0.00034

Measured yesterday against content hash 7f523186c1ae, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

flow-start 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.

plugins/git-flow/commands/flow-start.md · 40 lines

What it actually says

Start a new feature, bugfix, or hotfix branch following git-flow conventions.

Steps

  1. Determine the flow type from the argument:
    • feature/<name> for new features (branches from develop or main).
    • bugfix/<name> for non-critical fixes (branches from develop).
    • hotfix/<name> for critical production fixes (branches from main).
  2. Verify the working tree is clean: git status --porcelain.
  3. Fetch latest from remote: git fetch origin.
  4. Create the branch from the appropriate base:
    • git checkout -b <type>/<name> origin/<base>.
  5. Set up branch tracking: git push -u origin <type>/<name>.
  6. If a GitHub issue is referenced, link it:
    • Name the branch <type>/<issue-number>-<description>.
  7. Display the branch info and next steps.

Format

Flow started:
  Type: <feature|bugfix|hotfix>
  Branch: <branch-name>
  Base: <base-branch>
  Tracking: origin/<branch-name>

Next steps:
  1. Make your changes
  2. Commit with conventional messages
  3. Run: /git-flow:flow-release to merge

Rules

  • Always branch from a clean, up-to-date base branch.
  • Use lowercase kebab-case for branch names.
  • Include issue number in branch name when applicable.
  • Hotfix branches must always branch from the production branch.
  • Verify no branch with the same name already exists.
Changes

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.

  1. yesterday First seen · 40 lines · 0 tokens per session scan A 7f523186c1ae

Subscribe to this mod's changes

flow-start 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 340 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.