agentmods.dev

create-feature-branch

create-feature-branch is a command for Claude Code, Cursor from jabrena/plinth. It costs 11 tokens per session (641 once invoked), scanned A, original, Apache-2.0.

A command for creating and switching to a Git feature branch with a consistent name. A Git branch is a separate line of work that keeps changes isolated from the main code.

In plain words
What is it for?
Use it before issue fixes, new features, refactoring, documentation, analysis, or other repository changes.
Why use it?
It avoids unclear branch names and connects development work to an issue or OpenSpec change when one exists.

Command for Claude CodeCursor

Written for Claude Code and Cursor: argument-hint in frontmatter, but also installed under .cursor/. Also seen: model in frontmatter.

not rated 460repo +3 yesterday A scan 11 tokens original Apache-2.0

Good fit Use it before issue fixes, new features, refactoring, documentation, analysis, or other repository changes.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/jabrena/plinth/create-feature-branch
View source ↗ jabrena/plinth jabrena.github.io
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/jabrena/plinth

Made for: Claude Code, Cursor.

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

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

Your own site · 80×15
<a href="https://agentmods.dev/commands/jabrena/plinth/create-feature-branch"><img src="https://agentmods.dev/badge/commands/jabrena/plinth/create-feature-branch.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 11 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 641 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.00011 $0.00641
Opus 5.5 $0.00004 $0.00256
Sonnet 5.5 $0.00002 $0.00128
Haiku 4.5 $0.00001 $0.00064

Measured 2mo ago against content hash 28d0161747f3, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

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

.cursor/commands/create-feature-branch.md · 67 lines

How it starts

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

create-feature-branch

Create and switch the current checkout to a conventionally named local branch for GitHub issue, OpenSpec, analysis, design, documentation, or implementation work.

Usage

/create-feature-branch <issue-or-change|type description> [<base-reference>]

Accepted Inputs

  • An issue/change identifier, or an explicit branch type and description
  • Optional base reference
  • Supported branch types: feat, fix, docs, refactor, and chore
  • Preferred branch format: <type>/<issue-or-change>-<kebab-case-description> when an issue or OpenSpec change is available, otherwise <type>/<kebab-case-description>

Owning Agent

@plinth-tech-lead

Associated Capabilities

  • Git branch naming and validation
  • GitHub issue and OpenSpec change traceability
  • Analysis/design-to-implementation transition
  • Safe handling of existing local work

Workflow

  1. Read the repository instructions and resolve the branch type, issue/change identifier, and kebab-case description from the request.
  2. Prefer GitHub issue or OpenSpec change identifiers for traceable work; for complex architectural changes, keep the branch aligned to the OpenSpec change name.
  3. Resolve the repository default branch and the current branch.
  4. Verify the current checkout is main or the repository default branch before creating the new branch.
  5. If the current branch is not main or the default branch, stop and ask whether to switch to the default branch, choose a different base, or continue explicitly from the current branch.
  6. Verify the repository, selected base reference, branch name, and a safe working tree before changing the current checkout.
  7. Stop if the proposed branch already exists or is checked out in another worktree.
  8. Create and switch to the conventionally named local branch.
  9. Report the branch name, base reference, working tree status, and traceability source used to derive the branch.

Output

  • Created local branch
  • Confirmation with the exact branch name and base reference
  • Working tree status and any traceability source used for naming
  • A checkout ready for GitHub issue follow-up, OpenSpec artifacts, ADRs, diagrams, documentation, or application code

Read the full file on GitHub · 67 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. 2mo ago First seen · 67 lines · 11 tokens per session scan A 28d0161747f3

Subscribe to this mod's changes

create-feature-branch is a command published in the GitHub repository jabrena/plinth (460 stars, last pushed yesterday), licensed Apache-2.0. It adds 11 tokens to every session and 641 once invoked, about $0.0000 per session on Opus 5.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-30.

Claude CodeGit and workflowJavaclaude-code-skillsclaude-skillscursor-aigithub-copilot
Related

create-feature-branch compared with commands from other repositories

create-feature-branch next to 6 commands from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
create-feature-branchjabrena/plinthCommand460yesterdayApache-2.0A11Claude Code, Cursor
pralirezarezvani/claude-skillsCommand29kyesterdayMITA9Claude Code
cpalirezarezvani/claude-skillsCommand29kyesterdayMITA14Claude Code
make-prsergeyklay/.agentsCommand62d agoApache-2.0A10Claude Code
shipvignesh2027/claude-best-practiceCommand42mo agononeA0Claude Code
odoo-reviewomas-odoo/odoo-superpowersCommand14mo agononeB34Claude Code
checklistgithub/spec-kitCommand148kyesterdayMITA13Claude Code