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 agentmods add skills/tmj-90/gaffer/create-branchnpx skills add tmj-90/gaffer --skill create-branchgit clone --depth 1 https://github.com/tmj-90/gafferWrote 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/tmj-90/gaffer/create-branch)<a href="https://agentmods.dev/skills/tmj-90/gaffer/create-branch"><img src="https://agentmods.dev/badge/skills/tmj-90/gaffer/create-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 | $0.00050 | $0.01364 |
| Opus 5 | $0.00025 | $0.00682 |
| Sonnet 5 | $0.00010 | $0.00273 |
| Haiku 4.5 | $0.00005 | $0.00136 |
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 4d 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 — 101 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Get onto the working branch
All work happens on a prefixed feature branch — never on a protected branch
(main/master/release/*). The safety hook blocks pushes to protected branches.
Two paths — know which one you're in:
- In the factory (the normal case): the runner has ALREADY created your
gaffer/…branch and checked you out onto its worktree. You do not create or switch branches — you verify you're on the right kind of branch and stop if you aren't. See Factory path below. - Standalone / non-factory: no branch was prepared for you, so you create one yourself with the exact convention. See Standalone path below.
Factory path — VERIFY, do not create
The runner already created and checked you out onto your gaffer/ticket-<number>-…
worktree branch. Your job is to confirm the ground is safe, not to branch:
- Confirm you're on a non-protected branch. Check the current branch
(
git branch --show-current/git rev-parse --abbrev-ref HEAD). It must NOT bemain/master/release/*. Thegaffer/prefix is expected. - Do NOT run
git switch -c/git checkout -b. A branch already exists; creating another one diverges from the worktree the runner set up and the factory expects. - Check the working tree is clean. Run
git status --porcelain. If it is dirty — uncommitted or untracked state left over from a prior partial run on this worktree — do not branch over it or start editing on top of it. Stop andmark_ticket_blockedwith a clear reason ("worktree dirty on arrival: "); a human resolves the stale state. Fabricating a clean start over dirty state corrupts the delivery. - If you are somehow on a protected branch (the runner's setup didn't take), do not
"fix" it by creating your own branch —
mark_ticket_blockedand report it, because the environment isn't what the factory guarantees.
Once you've verified a clean tree on a non-protected gaffer/… branch, implement directly
on it. The rest of this skill (the naming convention) applies to the standalone case.
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.
- 4d ago First seen · 101 lines · 50 tokens per session scan A 22b65a840b7b
create-branch is a skill published in the GitHub repository tmj-90/gaffer (2 stars, last pushed 4d ago), licensed Apache-2.0. It adds 50 tokens to every session and 1,364 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-31.
Other skills, from other repositories
mobile-developer
Expert knowledge in mobile app development for iOS, Android, and cross-platform solutions.
skill-creator
Create or update AnkaLoop skills. Use when designing, structuring, or packaging skills with scripts, references, and assets. This skill should be used when users want to create a new skill (or update an existing skill) that extends AnkaLoop's capabilities with specialized knowledge, workflows, or tool integrations.
ai-engineer
Expert knowledge in AI/ML development, model deployment, and MLOps practices.
gh-ci-analyzer
使用 gh CLI 分析 GitHub Actions CI 日志，提供结构化的故障诊断和报告.
security-best-practices
Security best practices and vulnerability prevention guidelines.
react-developer
Expert knowledge in React development, hooks, state management, and modern React patterns.