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 ruchernchong/claude-kit --skill create-branchgit clone --depth 1 https://github.com/ruchernchong/claude-kitWrote 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/ruchernchong/claude-kit/create-branch)<a href="https://agentmods.dev/skills/ruchernchong/claude-kit/create-branch"><img src="https://agentmods.dev/badge/skills/ruchernchong/claude-kit/create-branch.svg" alt="Measured on agentmods" height="20"></a>- Socket pass
- Snyk warn
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.00019 | $0.01580 |
| Opus 5 | $0.00010 | $0.00790 |
| Sonnet 5 | $0.00004 | $0.00316 |
| Haiku 4.5 | $0.00002 | $0.00158 |
Grade A, and why
create-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 7d 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 — 206 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Language Conventions
Infer language style from the project:
- Analyze existing branches, commit messages, and documentation to detect the project's language variant (US English, UK English, etc.)
- Match the spelling conventions found in the project (e.g., "synchronize" vs "synchronise", "center" vs "centre")
- Maintain consistency with the project's established language style throughout branch names and command outputs
Create Branch Command
This command creates and checks out a new git branch with intelligent validation and GitHub issue integration.
Priority: GitHub Issue Integration
IMPORTANT: If the user provides an issue number (e.g., "#123", "123", or "issue 123"), ALWAYS prioritise using GitHub CLI's issue development workflow:
-
Check for GitHub CLI availability:
gh --versionIf not available, inform the user and fall back to manual branch creation.
-
Verify the issue exists:
gh issue view <issue-number>Display issue title and status to confirm.
-
Create branch linked to issue:
gh issue develop <issue-number> -c- The
-cflag automatically checks out the newly created branch - GitHub automatically generates an appropriate branch name from the issue title
- The branch is linked to the issue for better project tracking
- The
-
Skip to remote push step (step 8 below)
Manual Branch Creation Workflow
If no issue number is provided, follow this workflow:
1. Check Repository Status
git status
Verify:
- Clean working directory or acceptable uncommitted changes
- Current branch information
- Whether we're in a git repository
2. Get Branch Name Input
Ask the user for the desired branch name. Accept input in any format - the command will handle formatting and validation.
3. Auto-Detect and Apply Prefix
Analyse the branch name input for keywords and automatically add appropriate prefixes:
- feature/ - Keywords: "add", "implement", "create", "new", "feature"
- bugfix/ - Keywords: "fix", "bug", "resolve", "patch", "repair"
- hotfix/ - Keywords: "hotfix", "urgent", "critical", "emergency"
- chore/ - Keywords: "chore", "refactor", "update", "upgrade", "maintain"
- docs/ - Keywords: "docs", "documentation", "readme", "guide"
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.
- 7d ago First seen · 206 lines · 19 tokens per session scan A 8116c872952b
create-branch is a skill published in the GitHub repository ruchernchong/claude-kit (0 stars, last pushed 3mo ago), licensed MIT. It adds 19 tokens to every session and 1,580 once invoked, about $0.0001 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-09-01.
Other skills, from other repositories
ez-workflow
Use when about to run git branching, commit, push, or PR operations in a repo managed by ez-stack. Provides the complete command reference and agent-specific usage patterns.
creating-pr
Creates pull requests with quality descriptions. Use when asked to create a PR, open a pull request, or ship code for review. Requires test verification before PR creation.
committing
Creates quality git commits with conventional commit format. Use when asked to commit changes or create a commit message.
git-a2a
Use for git module dependencies, a2amodule.yml, dependency owners, contacts, status, and the managed AGENTS.md roster.
git-a2a
Use git-a2a to consume or author a dependency on a Git repository together with its owner, resolve who owns a dependency, inspect or repair an AGENTS.md module roster, or edit and validate a2amodule.yml manifest.
opensource
Open-source pipeline: fork, sanitize, and package private projects for safe public release. Chains 3 agents (forker, sanitizer, packager). Triggers: '/opensource', 'open source this', 'make this public', 'prepare for open source'.