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 mir-am/skills-agents-ai-coding --skill git-branchgit clone --depth 1 https://github.com/mir-am/skills-agents-ai-codingWrote 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/mir-am/skills-agents-ai-coding/git-branch)<a href="https://agentmods.dev/skills/mir-am/skills-agents-ai-coding/git-branch"><img src="https://agentmods.dev/badge/skills/mir-am/skills-agents-ai-coding/git-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.00021 | $0.01236 |
| Opus 5 | $0.00010 | $0.00618 |
| Sonnet 5 | $0.00004 | $0.00247 |
| Haiku 4.5 | $0.00002 | $0.00124 |
Grade A, and why
git-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 — 137 lines — stays where its author put it; the contents beside it link to each section on GitHub.
What I do
- Detect the repository default branch from
origin/HEAD, then fall back to localmain,master, ordevelop - Review the current session context plus staged and unstaged git changes to infer the branch purpose
- Generate a short branch name in
<type>/<brief-description>format - Create and switch to the new branch while preserving local changes when safe
- Ask the user instead of guessing when the intent or safe branching base is ambiguous
When to use me
Use this skill when the user asks to create a new git branch for the current work and wants the branch name derived from the session context and current git changes.
Prerequisites
gitmust be installed- Use
git switchwhen available; if the installed Git is too old to support it, usegit checkout/git checkout -binstead - The repository should have a detectable default branch from
origin/HEADor localmain,master, ordevelop - If the current branch is not the detected default branch and the worktree is dirty, ask the user before switching branches
Default Branch Detection
-
Check the current branch:
git branch --show-current -
Detect the remote default branch first:
default_branch="$(git symbolic-ref --quiet --short refs/remotes/origin/HEAD 2>/dev/null)" default_branch="${default_branch#origin/}" -
If the remote default branch is unavailable, fall back in this order:
for candidate in main master develop; do if git show-ref --verify --quiet "refs/heads/$candidate"; then default_branch="$candidate" break fi done -
If no default branch can be determined, stop and ask the user which branch should be used as the base.
Change Analysis
- Review the current agent session context and the user's latest request.
- Inspect the current git-visible work:
git status --short git diff --cached --stat git diff --stat - Prefer the user request and session goal over raw filenames when naming the branch.
- Use changed files and diff summaries as supporting context to infer the branch type and slug.
- If there are no local changes yet, derive the branch name from the session goal alone.
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 · 137 lines · 21 tokens per session scan A 02030d11297c
git-branch is a skill published in the GitHub repository mir-am/skills-agents-ai-coding (2 stars, last pushed 4mo ago), licensed MIT. It adds 21 tokens to every session and 1,236 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-08-31.
Other skills, from other repositories
skill-upstream-pr
Improve an open-source GitHub skill and open a friendly suggestion PR upstream: fork, run skill-auto-improver, attach asm eval before/after metrics. Don't use for local-only skills, authoring from scratch, bulk repos, or registry publish.
work
Pick up ready leaf yaks and implement them — dispatch subagents in isolated worktrees, then merge back to main.
yak-worktree-workflow
Use when starting work on a yak - sets up an isolated git worktree, reads yak context, and guides the full cycle from claiming through merge and cleanup.
swe-worktree
Create an isolated git worktree for an SWE change workspace. Use before implementation when the user wants the change isolated from the current working tree.
git
Use when user asks for git operations: branch creation, committing changes, creating pull requests.
finishing-a-development-branch
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup.