excel-mcp: Command for Claude Code

.claude/commands/prp-core/prp-core-new-branch.md

prp-core-new-branch is a command for Claude Code from mort-lab/excel-mcp. It costs 0 tokens per session (804 once invoked), scanned A, original, MIT.

A command that creates a new Git branch from the current branch using a short, conventional name based on the requested work. Git branches are separate lines of development used to organize changes.

In plain words
What is it for?
Use it to inspect the current branch, choose a prefix such as feature, fix, or documentation, turn the request into kebab-case, and create the branch.
Why use it?
It removes the need to invent branch names and helps keep branches consistent with the type of work being done.

Command for Claude Code

Written for Claude Code: installed under .claude/. Also seen: positional $N argument.

This is mort-lab/excel-mcp's own configuration. It tells Claude Code how to work on excel-mcp 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 excel-mcp configures →

Reuse

Borrowing it

Nothing to install: this file belongs to mort-lab/excel-mcp. 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/mort-lab/excel-mcp/main/.claude/commands/prp-core/prp-core-new-branch.md
Clone the repo
git clone --depth 1 https://github.com/mort-lab/excel-mcp

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 prp-core-new-branch

README.md
[![agentmods](https://agentmods.dev/badge/commands/mort-lab/excel-mcp/prp-core-new-branch/github.svg)](https://agentmods.dev/commands/mort-lab/excel-mcp/prp-core-new-branch)
Your own site
<a href="https://agentmods.dev/commands/mort-lab/excel-mcp/prp-core-new-branch"><img src="https://agentmods.dev/badge/commands/mort-lab/excel-mcp/prp-core-new-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 prp-core-new-branch

Your own site · 80×15
<a href="https://agentmods.dev/commands/mort-lab/excel-mcp/prp-core-new-branch"><img src="https://agentmods.dev/badge/commands/mort-lab/excel-mcp/prp-core-new-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 804 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.00804
Opus 5 $0.00000 $0.00402
Sonnet 5 $0.00000 $0.00161
Haiku 4.5 $0.00000 $0.00080

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

Security

Grade A, and why

prp-core-new-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 10d 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/prp-core/prp-core-new-branch.md · 104 lines

How it starts

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

Create Git Branch

Generate a conventional branch name based on user request and create a new git branch.

Variables

User request: $1

Instructions

Step 1: Check Current Branch

  • Check current branch: git branch --show-current
  • Check if on main/master:
    CURRENT_BRANCH=$(git branch --show-current)
    if [[ "$CURRENT_BRANCH" != "main" && "$CURRENT_BRANCH" != "master" && "$CURRENT_BRANCH" != "development" ]]; then
      echo "Warning: Currently on branch '$CURRENT_BRANCH', not main/master/development"
      echo "Proceeding with branch creation from current branch"
    fi
    
  • Note: We proceed regardless, but log the warning

Step 2: Generate Branch Name

Use conventional branch naming:

Prefixes:

  • feat/ - New feature or enhancement
  • fix/ - Bug fix
  • chore/ - Maintenance tasks (dependencies, configs, etc.)
  • docs/ - Documentation only changes
  • refactor/ - Code refactoring (no functionality change)
  • test/ - Adding or updating tests
  • perf/ - Performance improvements

Naming Rules:

  • Use kebab-case (lowercase with hyphens)
  • Be descriptive but concise (max 50 characters)
  • Remove special characters except hyphens
  • No spaces, use hyphens instead

Examples:

  • "Add user authentication system" → feat/add-user-auth
  • "Fix login redirect bug" → fix/login-redirect
  • "Update README documentation" → docs/update-readme
  • "Refactor database queries" → refactor/database-queries
  • "Add unit tests for API" → test/api-unit-tests

Branch Name Generation Logic:

  1. Analyze user request to determine type (feature/fix/chore/docs/refactor/test/perf)
  2. Extract key action and subject
  3. Convert to kebab-case
  4. Truncate if needed to keep under 50 chars
  5. Validate name is descriptive and follows conventions

Step 3: Check Branch Exists

  • Check if branch name already exists:
    if git show-ref --verify --quiet refs/heads/<branch-name>; then
      echo "Branch <branch-name> already exists"
      # Append version suffix
      COUNTER=2
      while git show-ref --verify --quiet refs/heads/<branch-name>-v$COUNTER; do
        COUNTER=$((COUNTER + 1))
      done
      BRANCH_NAME="<branch-name>-v$COUNTER"
    fi
    
  • If exists, append -v2, -v3, etc. until unique

Read the full file on GitHub · 104 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. 10d ago First seen · 104 lines · 0 tokens per session scan A 6f252c92bbda

Subscribe to this mod's changes

prp-core-new-branch is a command published in the GitHub repository mort-lab/excel-mcp (5 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 804 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.