Borrowing it
Nothing to install: this file belongs to egregore-labs/egregore. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/egregore-labs/egregore/main/.claude/skills/branch/SKILL.mdgit clone --depth 1 https://github.com/egregore-labs/egregoreWrote 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/egregore-labs/egregore/branch)<a href="https://agentmods.dev/skills/egregore-labs/egregore/branch"><img src="https://agentmods.dev/badge/skills/egregore-labs/egregore/branch/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/egregore-labs/egregore/branch"><img src="https://agentmods.dev/badge/skills/egregore-labs/egregore/branch.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.00032 | $0.01318 |
| Opus 5 | $0.00016 | $0.00659 |
| Sonnet 5 | $0.00006 | $0.00264 |
| Haiku 4.5 | $0.00003 | $0.00132 |
Grade A, and why
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 6d 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 — 148 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create a working branch from what you're working on.
When to invoke
User says: "/branch", "create a branch", "start a new branch", or any request to begin a working branch for what they're about to do
Description: $ARGUMENTS
What to do
Resolve the core repo's configured base first:
BASE_BRANCH=$(bash -c 'SCRIPT_DIR="$PWD"; CONFIG="$PWD/egregore.json"; . "$PWD/bin/lib/config.sh" && _get_base_branch') ||
{ echo "Could not resolve the configured base branch; stopping before Git changes." >&2; exit 1; }
- Derive a topic slug from the description (lowercase, hyphens, no special chars, max 40 chars)
- Determine branch type from description:
dev/{author}/{topic-slug}— default for session workfeature/{topic-slug}— explicit feature workbugfix/{topic-slug}— bug fixes
- Call
EnterWorktreewithnameset to the topic slug
The WorktreeCreate hook handles everything: fetches the configured base branch, creates the branch, creates the worktree, sets up symlinks.
Fallback: If EnterWorktree fails, fall back to: git checkout --no-track -b {branch-name} "origin/$BASE_BRANCH"
The task branch must not inherit origin/$BASE_BRANCH as its upstream. Its
first push uses git push -u origin "$BRANCH", which creates and tracks the
same-name remote task branch.
Deriving the topic slug
Extract the essence of what the user said into a short, meaningful slug:
- "auth flow in frontend" →
auth-flow - "fix the payment endpoint bug" →
fix-payment-endpoint - "refactoring the token store" →
refactor-token-store - "working on oauth implementation" →
oauth-implementation
If no description is given, use today's date: YYYY-MM-DD
Branch type detection
- Description mentions "fix", "bug", "broken", "crash" →
bugfix/ - Description mentions "feature", "add", "implement", "new" →
feature/ - Otherwise →
dev/{author}/(general session work)
Resuming existing branches
Before creating, check if a matching branch already exists:
git branch --list "dev/$AUTHOR/*$SLUG*" "feature/*$SLUG*" "bugfix/*$SLUG*"
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.
- 6d ago Changed · +4 lines ad1e92b86711
- 10d ago First seen · 144 lines · 32 tokens per session scan A 6d82968c5f1f
branch is a skill published in the GitHub repository egregore-labs/egregore (289 stars, last pushed 6d ago), licensed MIT. It adds 32 tokens to every session and 1,318 once invoked, about $0.0002 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
gwm
Manage git worktrees across any repository with the gwm Rust binary (CLI + ratatui TUI). Use when the user asks to create / list / remove / bootstrap / switch / link worktrees, run a command across worktrees (gwm exec) or reclaim build artifacts (gwm clean), materialise a PR into a worktree (gwm review), drive a…
agentplane
Use when a repository uses AgentPlane or the user wants a governed git-native workflow for planning, task execution, verification, and closure.
aigon-next
Suggest the most likely next workflow action based on current context.
dos-verify-done-claims
Before accepting an agent's 'done / shipped / fixed' claim, verify it against ground truth (git ancestry + the commit's own diff) using the DOS kernel's dos verify and dos commit-audit — never the agent's own narration.
take-task
A workflow for claiming a tracker task and preparing the development branch for it. It verifies the task, marks it as in progress, checks for uncommitted changes, and handles branch setup according to the task state.
release
Release Aigon — push to origin, cut a version+tag, or publish to npm. Wraps scripts/ship.js with CHANGELOG draft + dry-run preview. Triggers when the user types "/release", "/push", "/ship", or says "ship a release", "publish a beta", "cut a version", "push to origin", "release X to npm".