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/fmind/dot/feature-branchnpx skills add fmind/dot --skill feature-branchgit clone --depth 1 https://github.com/fmind/dotWrote 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/fmind/dot/feature-branch)<a href="https://agentmods.dev/skills/fmind/dot/feature-branch"><img src="https://agentmods.dev/badge/skills/fmind/dot/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 | $0.00033 | $0.00558 |
| Opus 5 | $0.00016 | $0.00279 |
| Sonnet 5 | $0.00007 | $0.00112 |
| Haiku 4.5 | $0.00003 | $0.00056 |
Grade A, and why
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 yesterday.
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.
What it actually says
Feature Branch
Create and switch to a <type>/<slug> branch off main for the work the user described; conventional-commit owns the commits that follow.
Workflow
-
Ask when the work is undescribed: without a description, an issue reference, or a desired branch name, ask and stop.
-
Inspect the tree:
git branch --show-current # current branch git status --short # uncommitted changes -
Derive the name as
<type>/<slug>:<type>: a commit type from conventional-commit, usuallyfeat,fix,chore,docs,refactor,test,perf, orci.<slug>: lowercase ASCII kebab-case, under 50 characters, no trailing punctuation.
-
Reuse a valid name: when the user's input already is a valid branch name, use it as is.
-
Confirm the base: off a branch other than
main(or the default branch), warn and ask first. -
Confirm a dirty tree: uncommitted changes move with the new branch; surface them and ask before continuing.
-
Create and switch; if the branch already exists, stop and report it:
git switch -c <branch> -
Report only these two lines after success:
Branch: <branch> From: <parent-branch>
Gotchas
- No push: the branch stays local; github-pull-request pushes it with
-uwhen the PR is opened.
Documentation
- Conventional Branch
- Companion skills: conventional-commit (commit on the branch), github-pull-request (open the PR).
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.
- yesterday First seen · 53 lines · 33 tokens per session scan A edfc946d15e5
feature-branch is a skill published in the GitHub repository fmind/dot (4 stars, last pushed today), licensed MIT. It adds 33 tokens to every session and 558 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-09-03.
Other skills, from other repositories
go-stack
Build Go projects, libraries, CLIs, TUIs, web apps, or ADK agents with the standard package layout and pinned tooling.
python-stack
Build typed Python projects with uv, Ruff, ty, pytest, Litestar, and Typer. Use for packages, CLIs, web apps, tests, typing, or API verification.
k8s-local
Create and manage local Kubernetes clusters (k3d or kind) and deploy to them with kubectl, helm, helmfile, and skaffold. Use for local k8s cluster setup, dev loops, and debugging.
chezmoi
Manage chezmoi dotfiles: source naming, Go templates, age-encrypted secrets, and the edit-source then apply/diff workflow.
hugo
Canonical Hugo static-site stack with the Hextra docs theme — Hugo Modules, mise tasks, dprint, lefthook, and GitHub Pages deploy. Use for documentation sites, project docs, and static websites.
mise
Configure pinned mise tools and canonical install, format, check, test, build, and watch tasks shared by hooks and CI.