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.
git clone --depth 1 https://github.com/C0ntr0lledCha0s/claude-code-plugin-automationsWrote 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/c0ntr0lledcha0s/claude-code-plugin-automations/branch-start)<a href="https://agentmods.dev/commands/c0ntr0lledcha0s/claude-code-plugin-automations/branch-start"><img src="https://agentmods.dev/badge/commands/c0ntr0lledcha0s/claude-code-plugin-automations/branch-start.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.1 | $0.00010 | $0.01274 |
| Opus 5 | $0.00005 | $0.00637 |
| Sonnet 5 | $0.00002 | $0.00255 |
| Haiku 4.5 | $0.00001 | $0.00127 |
Grade A, and why
branch-start 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 7d 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 — 216 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Branch Start
Create a new branch following the configured branching strategy (gitflow, github-flow, etc.).
Usage
/branch-start feature auth # Create feature/auth from develop
/branch-start bugfix validation-error # Create bugfix/validation-error
/branch-start feature user-dashboard --issue 42 # With issue link
Arguments
-
First argument (required): Branch type
feature: New feature developmentbugfix: Bug fix (non-urgent)hotfix: Emergency production fixrelease: Release preparationdocs: Documentation changesrefactor: Code refactoring
-
Second argument (required): Branch name/description
- Will be formatted according to naming conventions
- Spaces converted to hyphens
- Made lowercase
-
--issue N (optional): Related issue number
- Creates branch as
feature/issue-42-name - Automatically links to the issue
- Creates branch as
Input validation: Branch type must match configured flow types. Name must follow naming conventions (lowercase, hyphens, max 64 chars).
Workflow
When this command is invoked:
-
Validate arguments:
- Check branch type is valid for configured strategy
- Validate name follows conventions
- Check issue exists if provided
-
Load configuration: Read branching-config.json for flow settings
-
Invoke managing-branches skill: Get branching expertise
-
Determine base branch:
- Gitflow: features from develop, hotfixes from main
- GitHub Flow: all branches from main
- Per configured flows
-
Generate branch name:
- Apply prefix based on type
- Include issue reference if provided
- Enforce naming conventions
-
Create the branch:
- Switch to base branch
- Pull latest from origin
- Create new branch
- Optionally push to origin
-
Link to issue (if provided):
- Add branch label to issue
- Update issue tracking
-
Show next steps:
- Recommended commit format
- Issue references to use
- How to finish the branch
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.
- 7d ago First seen · 216 lines · 10 tokens per session scan A 6f3918613905
branch-start is a command published in the GitHub repository C0ntr0lledCha0s/claude-code-plugin-automations (3 stars, last pushed 6mo ago), licensed MIT. It adds 10 tokens to every session and 1,274 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-31.
Other commands, from other repositories
commit
A command that examines staged Git changes and proposes a commit message using the Conventional Commits format, such as feat, fix, or docs. Git is a tool for tracking changes to code.
release-notes
Generate consistent, well-structured release notes from git history. Triggered on release tags following semver patterns (v..) to produce categorized changelog with breaking changes, features, fixes, and contributor attribution.
doctor
Diagnosticar y reparar problemas del framework Don Cheli, git y entorno. Usa cuando el usuario dice "doctor", "problemas del framework", "don cheli no funciona", "repair Don Cheli", "debug setup", "setup broken", "framework broken", "reparar entorno". Detecta y repara issues de configuración, git y dependencias…
repo-audit
Audit a codebase (local or remote GitHub/GitLab) against architecture principles and requirements, surfacing drift, risk, and missing decisions.
handoff
Export a Waybill Bundle by default, or import one when requested.
release-plan
A release-planning command for a software change. It documents the release scope, rollback plan, gradual or full rollout, and monitoring before waiting for human approval.