feature-branch

feature-branch is a command for Claude Code from KaelSensei/MagicAIBuilder. It costs 0 tokens per session (1,115 once invoked), scanned A, original, MIT.

A command workflow for creating and managing a Git feature branch, which is a separate line of development for a specific change.

In plain words
What is it for?
Use it to choose and validate a branch name, inspect the current Git state, read project progress, load Cursor rules, and follow the repository's branch and version workflow.
Why use it?
It standardizes branch setup and checks project rules and current work before development starts.

Command for Claude Code

Written for Claude Code: a Claude Code command (commands/*.md). Also seen: installed under .agents/ (shared by several agents); mentions Cursor.

Good fit Use it to choose and validate a branch name, inspect the current Git state, read project progress, load Cursor rules, and follow the repository's branch and version workflow.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/kaelsensei/magicaibuilder/feature-branch
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.

Clone the repo
git clone --depth 1 https://github.com/KaelSensei/MagicAIBuilder

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

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

Your own site · 80×15
<a href="https://agentmods.dev/commands/kaelsensei/magicaibuilder/feature-branch"><img src="https://agentmods.dev/badge/commands/kaelsensei/magicaibuilder/feature-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 1,115 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.01115
Opus 5 $0.00000 $0.00558
Sonnet 5 $0.00000 $0.00223
Haiku 4.5 $0.00000 $0.00112

Measured 9d ago against content hash 50d0add50e64, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

feature-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 9d 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.

.agents/commands/feature-branch.md · 176 lines

How it starts

The opening of the file, as written. The whole thing — 176 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Feature Branch Command – Branch Creation & Management Workflow

When /feature-branch <branch-name> or /feature-branch is invoked, immediately execute the following steps.


Step 1: Load Project Context & Follow All Rules

  1. Assume the project root as the working directory
  2. Load and strictly follow ALL Cursor rules from .cursor/rules/*.mdc:
    • security.mdc - Security requirements
    • technical-stack.mdc - React Native/SQLite patterns
    • documentation.mdc - Documentation update requirements
    • version-management.mdc - Git commit/push workflow
  3. Check current git status and branch
  4. Read PROGRESS.md to understand current project state

Step 2: Determine Branch Name

  1. If branch name provided: Use <branch-name> from command
  2. If no branch name provided:
    • Infer from current work context
    • Use format: feature/<description> or fix/<description>
    • Ask user for branch name if unclear
  3. Validate branch name:
    • Use lowercase with hyphens (e.g., feature/search-reset-button)
    • Avoid special characters or spaces
    • Keep it descriptive but concise

Step 3: Check Current State

  1. Check current branch:

    git branch --show-current
    
  2. Check for uncommitted changes:

    git status
    
  3. If uncommitted changes exist:

    • Commit them first (following version-management.mdc rules)
    • Or stash them if user prefers
    • Never create branch with uncommitted changes unless explicitly requested
  4. If on main/master:

    • Warn user (but proceed if confirmed)
    • Always create feature branch from main/master

Step 4: Create Feature Branch

  1. Ensure you're on the base branch (usually main or master):

    git checkout main  # or master
    git pull origin main  # or master
    
  2. Create and switch to new branch:

    git checkout -b <branch-name>
    
  3. Push branch to remote (set upstream):

    git push -u origin <branch-name>
    

Read the full file on GitHub · 176 lines

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. 9d ago First seen · 176 lines · 0 tokens per session scan A 50d0add50e64

Subscribe to this mod's changes

feature-branch is a command published in the GitHub repository KaelSensei/MagicAIBuilder (2 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,115 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.