create-branch

A command that creates a new Git branch from the latest main branch. Git branches are separate lines of work used to develop and review changes.

In plain words
What is it for?
Use it before starting work on a feature, fix, documentation change, test, or other repository update.
Why use it?
It provides a consistent branch name based on the change type, related issue, and a short description, while checking existing changes when present.

Command for Claude Code

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/aziontech/webkit/create-branch
Clone the repo
git clone --depth 1 https://github.com/aziontech/webkit

Made for: Claude Code.

Per session 26 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 550 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.00026 $0.00550
Opus 5 $0.00013 $0.00275
Sonnet 5 $0.00005 $0.00110
Haiku 4.5 $0.00003 $0.00055

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

Security

Grade A, and why

create-branch 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.

.claude/commands/create-branch.md · 32 lines

What it actually says

You are running /create-branch. Cut a fresh branch off the latest main, named from the change type + related issue + a short slug.

User input: $ARGUMENTS

Source of truth

Steps

  1. Sync. Run git fetch origin --prune.

  2. Read the change (if any). If the working tree already has changes, run git status and git diff and use them to infer the branch type and a slug. If the tree is clean, derive both from $ARGUMENTS (ask for a 2–4 word description if none was given).

  3. Type. Pick from the same enum the repo's commit convention uses: feat (default — new component/prop/event/export), fix, chore, docs, style, refactor, perf, test, ci, revert. Only feat / fix (or a breaking !) actually release (see release-types.md).

  4. Related issue (optional). Ask: "Which issue does this relate to? (ENG-1234, or leave blank if none)". A blank answer is fine — treat it as no issue (no tag anywhere; never [NO-ISSUE]). Do not block on it.

  5. Create.

    • With an issue: git checkout -b <type>/<ISSUE>-<slug> origin/main
    • Without: git checkout -b <type>/<slug> origin/main

    If uncommitted changes would block the checkout, stop and tell the user to commit or stash first — never discard their work.

  6. Confirm. Report the new branch name and that it is based on origin/main.

Rules

  • Always base on origin/main.
  • Branch name: lowercase kebab-case — <type>/<ISSUE>-<slug> (or <type>/<slug> when there is no issue). Example: feat/ENG-46315-toast.
  • Do not push or open a PR here — that is /open-pr's job.
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 · 32 lines · 0 tokens per session scan A 310d1285c21b

Subscribe to this mod's changes

create-branch is a command published in the GitHub repository aziontech/webkit (2 stars, last pushed 3d ago), licensed MIT. It adds 26 tokens to every session and 550 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-31.