agentmods.dev

webkit: Command for Claude Code

.claude/commands/create-branch.md

create-branch is a command for Claude Code from aziontech/webkit. It costs 0 tokens per session (550 once invoked), scanned A, original, MIT.

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

Written for Claude Code: argument-hint in frontmatter.

This is aziontech/webkit's own configuration. It tells Claude Code how to work on webkit itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything webkit configures →

not rated 3repo today A scan 0 tokens original MIT
View source ↗ aziontech/webkit
Reuse

Borrowing it

Nothing to install: this file belongs to aziontech/webkit. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/aziontech/webkit/main/.claude/commands/create-branch.md
Clone the repo
git clone --depth 1 https://github.com/aziontech/webkit

Made for: Claude Code.

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

README.md
[![agentmods](https://agentmods.dev/badge/commands/aziontech/webkit/create-branch/github.svg)](https://agentmods.dev/commands/aziontech/webkit/create-branch)
Your own site
<a href="https://agentmods.dev/commands/aziontech/webkit/create-branch"><img src="https://agentmods.dev/badge/commands/aziontech/webkit/create-branch/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.

agentmods 80×15 button for create-branch

Your own site · 80×15
<a href="https://agentmods.dev/commands/aziontech/webkit/create-branch"><img src="https://agentmods.dev/badge/commands/aziontech/webkit/create-branch.svg" alt="Reviewed on agentmods" width="80" 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 550 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00000 $0.00550
Opus 5.5 $0.00000 $0.00220
Sonnet 5.5 $0.00000 $0.00110
Haiku 4.5 $0.00000 $0.00055

Measured 2mo ago against content hash 310d1285c21b, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, 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 2mo 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.

.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. 2mo ago 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 (3 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 550 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-08-31.

Git and workflowcomponent-libraryfrontend-platformmonorepoui-architectureworkspace
Related

Other commands, from other repositories

arrange-workspace-flow-choose-workspace-layout

Phase 1 Choose Workspace Layout of arrange-workspace-flow.

griddynamics/rosetta · 22 tokens

scm

SCM workflow for Git operations (branching/merge/conflict/worktree) plus Conventional Commit execution.

first-fluke/fullstack-starter · 21 tokens

merge-conflict-analysis

You are analyzing merge conflicts for PR #${{ pr-number }}.

rjmurillo/ai-agents · 0 tokens

release-notes

Generate consistent, well-structured release notes from git history. Triggered on release tags following semver patterns (v..) to produce categorized changelog with breaking changes, features, fixes, and contributor attribution.

OpenHands/extensions · 44 tokens

repo-audit

Audit a codebase (local or remote GitHub/GitLab) against architecture principles and requirements, surfacing drift, risk, and missing decisions.

tractorjuice/arc-kit · 29 tokens

codex-review

Use when asked to check, turn on, turn off, or switch this repo's Codex review mode (local, github, or off), or to report the effective mode and Codex sandbox status.

oalders/kitchen-sink · 41 tokens