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 atman-33/workhub --skill create-feature-branchgit clone --depth 1 https://github.com/atman-33/workhubWrote 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/atman-33/workhub/create-feature-branch)<a href="https://agentmods.dev/skills/atman-33/workhub/create-feature-branch"><img src="https://agentmods.dev/badge/skills/atman-33/workhub/create-feature-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.00066 | $0.00588 |
| Opus 5 | $0.00033 | $0.00294 |
| Sonnet 5 | $0.00013 | $0.00118 |
| Haiku 4.5 | $0.00007 | $0.00059 |
Grade A, and why
create-feature-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 — 47 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create Feature Branch
Create a new feature branch for the user's next task in the intended repository.
Quick start
- Confirm the target repository root unless the calling workflow already resolved it.
- Ask what feature the branch should represent unless the user already gave a clear branch name.
- Turn the answer into a short branch name such as
feature/<name>. - Switch into the target repository root with
Push-Location/Pop-Locationor an equivalent directory stack. - Update the local
mainbranch to the latest state and create the new branch there.
Workflow
- Resolve the repository context.
- If a calling workflow already resolved a repository root or repository id, treat it as binding.
- If multiple repositories could apply, ask one narrow question before running any git command.
- Run
git rev-parse --show-toplevelin the working directory and stop if it does not match the intended repository. - Never rely on the shell's inherited current directory when the repository matters.
- Confirm the branch target.
- If the user gives a feature description, convert it to a concise kebab-case slug.
- If the user gives an exact branch name, use it when it matches the repository convention.
- If the repository uses a different prefix than
feature/, follow that convention.
- Sync
mainin the target repository.- Use
Push-Location/Pop-Locationor an equivalent directory stack when switching into the target repository root. - Switch to the local
mainbranch in that repository. - Update it from the default remote with a non-interactive command.
- Use
- Create the feature branch.
- Create the branch from the updated
mainbranch in the target repository. - Switch to the new branch immediately.
- Create the branch from the updated
- Report the result.
- Tell the user the final branch name.
- Tell the user which repository root the branch was created in.
- Surface blockers such as repository mismatches, uncommitted changes, missing remotes, or pull failures instead of guessing.
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 First seen · 47 lines · 66 tokens per session scan A 8047b5522bd8
create-feature-branch is a skill published in the GitHub repository atman-33/workhub (2 stars, last pushed yesterday), licensed MIT. It adds 66 tokens to every session and 588 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
gonavi-cli
Operate databases through the GoNavi headless CLI — the gonavi executable shipped in verified GitHub Release archives. Covers listing/adding/importing saved connections, running SQL queries against saved connections or ad-hoc connection files, exporting result sets to csv/json/md/html/xlsx, batch-executing SQL files…
procoder
Work like a senior developer in a repository governed by procoder: run the commit gate before calling anything done, format and lint through the binary, and drive the spec, plan, todo, backlog, and sprint chain in .procoder/. Use this skill when the repository contains a .procoder/ directory or an AGENTS.md naming…
detect-task
Internal skill for commands. Detect the active task (any tracker adapter) from the task-state file / git branch name. Do not trigger on user conversation - only when commands need task detection.
session-boundary
Internal skill for commands. Resolve and VALIDATE this branch's session boundary - the ref a session's commit range is measured from - and report how much it can be trusted. Do not trigger on user conversation; only when a command needs the session range.
document-release
Use when implementation on a branch is complete and it is about to be merged or PR'd — or when finishing-a-development-branch reaches its docs-audit gate — and after code changes are committed, to ensure all project documentation accurately reflects shipped code. Covers README, ARCHITECTURE, CONTRIBUTING, CHANGELOG…
pr-sweep
Use when you want to sweep all open pull requests across all repos, triage their status, run code reviews on unreviewed PRs, merge what's ready, fix quick blockers, and produce a full status report. Trigger when the user says "check my PRs", "close out open PRs", "what's the status of my PRs", "sweep my PRs", "PR…