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 artem-from-ua/claude-plugins --skill branch-naming-guidegit clone --depth 1 https://github.com/artem-from-ua/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/artem-from-ua/claude-plugins/branch-naming-guide)<a href="https://agentmods.dev/skills/artem-from-ua/claude-plugins/branch-naming-guide"><img src="https://agentmods.dev/badge/skills/artem-from-ua/claude-plugins/branch-naming-guide/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/artem-from-ua/claude-plugins/branch-naming-guide"><img src="https://agentmods.dev/badge/skills/artem-from-ua/claude-plugins/branch-naming-guide.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.00066 | $0.00673 |
| Opus 5 | $0.00033 | $0.00336 |
| Sonnet 5 | $0.00013 | $0.00135 |
| Haiku 4.5 | $0.00007 | $0.00067 |
Grade A, and why
branch-naming-guide 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 — 64 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Git Branch Naming Guide
Format
<prefix>/<kebab-case-description>
Prefix Reference
| Prefix | When to use | Example |
|---|---|---|
feature/ |
New functionality, user-facing changes | feature/user-auth |
bugfix/ |
Non-critical bug fixes | bugfix/fix-login-redirect |
hotfix/ |
Urgent production fixes | hotfix/fix-payment-crash |
release/ |
Release preparation | release/1.2.0 |
docs/ |
Documentation only | docs/update-api-readme |
test/ |
Tests only (no feature code) | test/add-auth-coverage |
chore/ |
Config, CI, deps, tooling | chore/upgrade-dependencies |
refactor/ |
Code restructuring (no behavior change) | refactor/extract-auth-service |
Rules
- Prefix required — always use one of the prefixes above
- Kebab-case — lowercase only, hyphens as separators, no underscores or spaces
- Descriptive — brief but clear (
feature/authis too short;feature/add-oauth2-google-loginis good) - Max 60 characters (project default, configurable)
- Ticket number — include if required by project config (e.g.,
feature/JIRA-123-add-oauth)
Quick Naming Tips
- Use present tense:
feature/add-loginnotfeature/added-login - Be specific:
bugfix/fix-null-pointer-in-cartnotbugfix/fix-bug - Skip "the", "a", "an":
feature/user-settingsnotfeature/the-user-settings-page
Good vs Bad Examples
| Bad | Good | Reason |
|---|---|---|
my-feature |
feature/my-feature |
Missing prefix |
Feature/UserAuth |
feature/user-auth |
Wrong case |
feature/user_auth |
feature/user-auth |
Underscore → hyphen |
fix |
bugfix/fix-login-error |
Too vague, missing prefix |
feature/implementing-the-new-very-long-user-authentication-flow-page |
feature/user-oauth-login |
Too long |
Checking Project Config
If .claude-plugin/git-branch-naming.json exists in the project, it may override:
- Allowed prefixes
- Required ticket pattern (e.g.,
JIRA-\d+,#\d+) - Max branch name length
- Enforcement mode (
askvsdeny)
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 · 64 lines · 66 tokens per session scan A e8b62bb95228
branch-naming-guide is a skill published in the GitHub repository artem-from-ua/claude-plugins (11 stars, last pushed 2d ago), licensed MIT. It adds 66 tokens to every session and 673 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-30.
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.