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.
curl -O https://raw.githubusercontent.com/mort-lab/excel-mcp/main/.claude/commands/prp-core/prp-core-new-branch.mdgit clone --depth 1 https://github.com/mort-lab/excel-mcpWrote 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.
[](https://agentmods.dev/commands/mort-lab/excel-mcp/prp-core-new-branch)<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.
<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>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.
| Model | Per session | Once 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 |
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.
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 enhancementfix/- Bug fixchore/- Maintenance tasks (dependencies, configs, etc.)docs/- Documentation only changesrefactor/- Code refactoring (no functionality change)test/- Adding or updating testsperf/- 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:
- Analyze user request to determine type (feature/fix/chore/docs/refactor/test/perf)
- Extract key action and subject
- Convert to kebab-case
- Truncate if needed to keep under 50 chars
- 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
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.
- 10d ago First seen · 104 lines · 0 tokens per session scan A 6f252c92bbda
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.
Other commands, from other repositories
CHANGELOG
Command "CHANGELOG" from bytedance/UI-TARS-desktop, covering 0.4.0 2024-12-10 - add logging, 1.2.29, 1.2.28, 1.2.26 and 1.2.25.
mega-approve
Approve the mega-plan and start feature execution. Creates worktrees and generates PRDs for each feature. Usage: /plan-cascade:mega-approve [--flow ] [--tdd ] [--confirm] [--no-confirm] [--spec ] [--first-principles] [--max-questions N] [--auto-prd] [--agent ] [--prd-agent ] [--impl-agent ].
improve
Run ONE iteration of the continuous-improvement loop — pick the highest-value backlog item, implement it, verify end-to-end, commit.
end
End the current collaboration session and release all claims.
bulk-add
Batch-shelve several repos at once — from a URL list or your GitHub stars — then draft honest notes for each.
enable-journaling
Opt-in setup for auto-journaling capture plumbing. Copies bundled PostToolUse hook scripts into .squad/hooks/ and prints the exact .claude/settings.json snippet to wire them up. Capture-only — squad behaviour does NOT change until a follow-up release adds distillation + retrieval. Triggers: "enable journaling", "turn…