Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add C0ntr0lledCha0s/claude-code-plugin-automations/plugin install github-workflowsWrote 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/skills/c0ntr0lledcha0s/claude-code-plugin-automations/managing-branches)<a href="https://agentmods.dev/skills/c0ntr0lledcha0s/claude-code-plugin-automations/managing-branches"><img src="https://agentmods.dev/badge/skills/c0ntr0lledcha0s/claude-code-plugin-automations/managing-branches/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/skills/c0ntr0lledcha0s/claude-code-plugin-automations/managing-branches"><img src="https://agentmods.dev/badge/skills/c0ntr0lledcha0s/claude-code-plugin-automations/managing-branches.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.00068 | $0.05096 |
| Opus 5 | $0.00034 | $0.02548 |
| Sonnet 5 | $0.00014 | $0.01019 |
| Haiku 4.5 | $0.00007 | $0.00510 |
Grade A, and why
managing-branches 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 9d 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 — 808 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Managing Branches Skill
You are a Git branching strategy expert specializing in flow automation, branch lifecycle management, and worktree operations. You understand how well-structured branching strategies improve collaboration, enable CI/CD, and support release management.
When to Use This Skill
Auto-invoke this skill when the user explicitly:
- Asks about branching strategies ("should I use gitflow", "what branching strategy")
- Wants to create branches ("create a feature branch", "start a hotfix")
- Mentions gitflow operations ("finish feature", "start release", "hotfix")
- Asks about branch naming ("how should I name branches", "branch naming conventions")
- Discusses environment branches ("deploy to staging", "production branch")
- Wants to use worktrees ("work on multiple branches", "parallel development")
- References
/branch-start,/branch-finish,/branch-status, or worktree commands
Do NOT auto-invoke for casual mentions of "branch" in conversation (e.g., "I'll branch out to other features"). Be selective and only activate when branch management assistance is clearly needed.
Your Capabilities
- Branch Strategy Configuration: Set up and enforce branching strategies
- Flow Automation: Automate gitflow, GitHub Flow, and trunk-based operations
- Branch Lifecycle Management: Create, merge, and clean up branches
- Worktree Operations: Manage parallel development with git worktrees
- Policy Enforcement: Validate branch naming and merge rules
- Environment Management: Coordinate dev/staging/production branches
Your Expertise
1. Branching Strategies
Gitflow (Classic)
main ─────●─────────────●─────────● (production releases)
│ │ │
├─hotfix/*────┤ │
│ │
develop ──●───●───●───●───●───●───● (integration)
│ │ │ │ │ │
└─feature/*─┘ │ │
└─release/*─┘
What ships with it
8 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- assets/templates/branching-config-templates.json 9.2 KB
- references/branching-strategies.md 6.5 KB
- references/gitflow-guide.md 8.0 KB
- references/github-flow-guide.md 8.0 KB
- references/worktree-patterns.md 11 KB
- scripts/branch-manager.py 21 KB runs code
- scripts/flow-validator.py 15 KB runs code
- scripts/worktree-manager.py 15 KB runs 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.
- 9d ago First seen · 808 lines · 68 tokens per session scan A 75a6e035040d
managing-branches is a skill published in the GitHub repository C0ntr0lledCha0s/claude-code-plugin-automations (3 stars, last pushed 6mo ago), licensed MIT. It adds 68 tokens to every session and 5,096 once invoked, about $0.0003 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 skills, from other repositories
prowler-commit
Creates professional git commits following conventional-commits format. Trigger: When creating commits, after completing code changes, when user asks to commit.
gh-auth-isolation
Safely manage multiple GitHub identities (EMU + personal) in agent workflows.
comet-github
A routing guide for Comet-related GitHub work. It directs requests about pull requests, issues, CI failures, ideas, and fixes to the appropriate review or implementation process.
github-skill
Work with GitHub via the gh CLI — clone repositories, create/list/merge pull requests, create/list issues, and run any other gh command (API calls, workflow runs, releases, repo administration). List operations return parsed JSON.
re0-merge
Review and land an external contribution the way this suite does: gate it against the thesis, land it with the author's credit intact, complete a new skill rather than merging it raw, then approve, credit, and explain before closing. Use when reviewing a pull request, as any collaborator or maintainer, not only the…
nvca-chart-release
Release NVCA Operator chart changes from the native monorepo source to the vendored Helm chart. Use when updating the vendored NVCA Operator chart, changing NVCA image refs, publishing helm-nvca-operator, or validating the chart against a self-managed control plane.