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 thedesignproject/agent-skills --skill pr-branch-naminggit clone --depth 1 https://github.com/thedesignproject/agent-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/thedesignproject/agent-skills/pr-branch-naming)<a href="https://agentmods.dev/skills/thedesignproject/agent-skills/pr-branch-naming"><img src="https://agentmods.dev/badge/skills/thedesignproject/agent-skills/pr-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/thedesignproject/agent-skills/pr-branch-naming"><img src="https://agentmods.dev/badge/skills/thedesignproject/agent-skills/pr-branch-naming.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00079 | $0.01249 |
| Opus 5 | $0.00039 | $0.00624 |
| Sonnet 5 | $0.00016 | $0.00250 |
| Haiku 4.5 | $0.00008 | $0.00125 |
Grade A, and why
pr-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 12d 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 — 127 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PR & Branch Naming
You generate a conventionally-named branch and a matching PR title from a feature description, then optionally check out the branch and/or open a PR — but only with explicit user confirmation.
Step 1: Get the feature description
The user's input is in $ARGUMENTS. It can be:
- A description — use it directly
- Empty — try to infer the work from
git statusand the most recent commits (git log -n 5 --oneline). If you can infer it, propose it back to the user for confirmation. If not, ask: "What's the feature or change this branch is for?"
Don't fabricate a description. If there's nothing to go on, ask.
Step 2: Pick the type and scope
Type (one of)
| Type | When to use |
|---|---|
feat |
New feature or new UI work |
fix |
Bug fix to existing functionality |
docs |
Documentation changes only |
refactor |
Code restructuring with no behavior change |
perf |
Performance improvement |
chore |
Tooling, config, dependency bumps |
experimental |
Prototype, spike, or exploration not intended to ship as-is |
Pick the type that best matches the description. For designer-authored work, the common types are feat and experimental.
Scope
The area of the product affected — short, lowercase, single word if possible. Examples: playground, dashboard, auth, onboarding, billing.
Infer the scope from the description. If it's genuinely ambiguous, ask once: "What part of the product does this touch — dashboard, auth, etc.?" Don't pepper the user with questions.
Step 3: Pick the branch prefix
| Prefix | When to use |
|---|---|
feature/ |
New features or UI work (pairs with feat) |
bugfix/ |
Fixing existing functionality (pairs with fix) |
hotfix/ |
Urgent production fixes |
docs/ |
Documentation changes (pairs with docs) |
experimental/ |
Prototypes and explorations (pairs with experimental) |
The prefix should align with the type. Use feature/ for feat, bugfix/ for fix, and so on.
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.
- 12d ago First seen · 127 lines · 79 tokens per session scan A 44cf2ce170f1
pr-branch-naming is a skill published in the GitHub repository thedesignproject/agent-skills (86 stars, last pushed 17d ago), licensed MIT. It adds 79 tokens to every session and 1,249 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-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.
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…