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.
npx agentmods add commands/jabrena/plinth/create-feature-branchgit clone --depth 1 https://github.com/jabrena/plinthWrote 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/jabrena/plinth/create-feature-branch)<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="Measured on agentmods" 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 | $0.00011 | $0.00641 |
| Opus 5 | $0.00005 | $0.00320 |
| Sonnet 5 | $0.00002 | $0.00128 |
| Haiku 4.5 | $0.00001 | $0.00064 |
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 5d 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 — 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, andchore - 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
- Read the repository instructions and resolve the branch type, issue/change identifier, and kebab-case description from the request.
- Prefer GitHub issue or OpenSpec change identifiers for traceable work; for complex architectural changes, keep the branch aligned to the OpenSpec change name.
- Resolve the repository default branch and the current branch.
- Verify the current checkout is
mainor the repository default branch before creating the new branch. - If the current branch is not
mainor the default branch, stop and ask whether to switch to the default branch, choose a different base, or continue explicitly from the current branch. - Verify the repository, selected base reference, branch name, and a safe working tree before changing the current checkout.
- Stop if the proposed branch already exists or is checked out in another worktree.
- Create and switch to the conventionally named local branch.
- 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
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.
- 5d ago First seen · 67 lines · 11 tokens per session scan A 28d0161747f3
create-feature-branch is a command published in the GitHub repository jabrena/plinth (435 stars, last pushed today), licensed Apache-2.0. It adds 11 tokens to every session and 641 once invoked, about $0.0001 per session on Opus 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.
Other commands, from other repositories
refactor
Systematic refactoring: analyze → split → extract → verify behavior, with no truncation or omitted lines.
auth-flows
Read-only audit of app-layer auth — route×gate matrix, getSession vs getUser, middleware-as-only-gate.
integrity-plan
Data-integrity & destructive-op audit — plan only, no migrations or tokens until approved.
review
Use when reviewing spec-forge generated documents for quality, completeness, and consistency — auto-fixes issues if found.
prd
Use when writing a PRD, product spec, or product requirements — follows Google/Amazon/Stripe methodologies.
idea
Use when exploring a new idea — validates demand, analyzes competitors, and checks for pseudo-requirements before writing specs.