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 vidhunnan/agentic-skills --skill branch-naminggit clone --depth 1 https://github.com/vidhunnan/agentic-skillsWrote 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/vidhunnan/agentic-skills/branch-naming)<a href="https://agentmods.dev/skills/vidhunnan/agentic-skills/branch-naming"><img src="https://agentmods.dev/badge/skills/vidhunnan/agentic-skills/branch-naming/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/vidhunnan/agentic-skills/branch-naming"><img src="https://agentmods.dev/badge/skills/vidhunnan/agentic-skills/branch-naming.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.00088 | $0.01186 |
| Opus 5 | $0.00044 | $0.00593 |
| Sonnet 5 | $0.00018 | $0.00237 |
| Haiku 4.5 | $0.00009 | $0.00119 |
Grade A, and why
branch-naming 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 11d 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 — 77 lines — stays where its author put it; the contents beside it link to each section on GitHub.
branch-naming
Names branches consistently. It figures out the project's branch convention, reads the current work context, proposes a conforming name, and — only after you confirm — can create the branch. The convention it uses is recorded in CLAUDE.md so it stays consistent across sessions and people.
This skill only Edits CLAUDE.md and creates branches via git — it authors no standalone files.
Instructions
Step 0 — Detect your surface
Using Bash availability:
- Claude Code — full flow (git + CLAUDE.md).
- Claude.ai — no git. You can still suggest names as text following whatever convention the user describes, but you can't read
git branch, read CLAUDE.md, or create the branch. Say so.
Confirm a git repo: git rev-parse --show-toplevel. If it fails, tell the user and stop.
Step 1 — Determine the convention (in priority order)
- From CLAUDE.md — Read the project's CLAUDE.md. If it states a branch convention (a
<!-- BEGIN skill:branch-naming -->block, or prose like<area>/<type>/<slug>), use it. - Infer from existing branches —
git branch -a. Detect the dominant pattern: number of segments, separator, casing, commontypetokens. Use the most common shape. - Help the user define one — if there's no signal, ask (AskUserQuestion) offering common shapes:
type/slug(e.g.feat/…),area/type/slug(e.g.web/feat/…),user/type/slug. Record the choice in CLAUDE.md via Step 5.
Step 2 — Gather the work context
Derive the name from real signals, not invention:
- The conversation (what's being worked on).
git statusandgit diff --name-only— which files/areas are touched.- The optional
[work-description]argument, if given.
Map these to the convention's parts: area (workstream/directory), type (feat/fix/chore/docs/… per the convention), slug (short kebab-case description).
Step 3 — Propose name(s) and confirm
Offer 1–3 candidates that conform to the convention. Present via AskUserQuestion so the user picks or edits one. Wait — never create a branch silently.
What ships with it
1 file 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.
- 11d ago First seen · 77 lines · 88 tokens per session scan A f5729d32c66d
branch-naming is a skill published in the GitHub repository vidhunnan/agentic-skills (2 stars, last pushed 5d ago), licensed MIT. It adds 88 tokens to every session and 1,186 once invoked, about $0.0004 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.
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".
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…