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 skills add sembraniteam/claude-plugins --skill generate-branchgit clone --depth 1 https://github.com/sembraniteam/claude-pluginsWrote 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/sembraniteam/claude-plugins/generate-branch)<a href="https://agentmods.dev/skills/sembraniteam/claude-plugins/generate-branch"><img src="https://agentmods.dev/badge/skills/sembraniteam/claude-plugins/generate-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.1 | $0.00068 | $0.01332 |
| Opus 5 | $0.00034 | $0.00666 |
| Sonnet 5 | $0.00014 | $0.00266 |
| Haiku 4.5 | $0.00007 | $0.00133 |
Grade A, and why
generate-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 6d 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 — 112 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Generate Branch Name
Generate a valid git branch name following team naming conventions. When invoked directly by the user, this skill will ask to create and switch to the branch after generating the name. When invoked via the Skill tool by generate-commit, it outputs the branch name only — the calling skill owns the checkout step.
Input Collection
Collect from the invocation and conversation context:
- Work description — what the user will work on (optional)
- File paths — from the argument, limits the diff to specific files (optional)
If no work description is provided, run these commands and infer a 2–5 word description from the staged diff (primary) or unstaged diff (secondary). Append -- <files> to scope diffs to specific paths. Do not ask — infer from diff:
git --no-pager log --oneline -10
git --no-pager status --short
git --no-pager diff [-- <files>]
git --no-pager diff --cached [-- <files>]
If the diff is empty and no description was provided, ask the user for a one-sentence description of the work.
If the description is provided but unclear (e.g., a single ambiguous word like "fix" with no additional context), ask one brief clarifying question before proceeding.
Branch Construction
Select prefix — choose the best match; default to feature/ when ambiguous:
| Prefix | When to use |
|---|---|
feature/ |
New feature development |
bugfix/ |
Non-urgent bug fix |
hotfix/ |
Urgent production fix |
release/ |
Release preparation (e.g., release/v1.2.0) |
chore/ |
Non-code tasks: docs, tooling, config |
bump/ |
Dependency/version update |
Build the slug from the work description:
- Extract 2–5 core words, lowercase, replace spaces and special chars with hyphens
- Remove leading/trailing and consecutive hyphens
- If scope implied by description: use
type/scope/slugformat
What ships with it
2 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.
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.
- 6d ago First seen · 112 lines · 68 tokens per session scan A a66c5f2e7359
generate-branch is a skill published in the GitHub repository sembraniteam/claude-plugins (2 stars, last pushed 1mo ago), licensed MIT. It adds 68 tokens to every session and 1,332 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.
codex-autoresearch
Run autonomous, measurable experiments in a Git repository: change one hypothesis, verify a numeric metric, keep improvements, and revert failures. Use when the user wants Codex to keep iterating toward a numeric target in the foreground or as a detached background run. Do not use for ordinary one-shot coding…
changelog-composer
Generates structured changelogs and release notes from git history and PRs, classifying breaking changes, features, fixes, performance, docs. Triggers on: "generate changelog", "write release notes", "what changed since", "prepare release", "release notes for", "diff since tag".