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/fusengine/agents/git-flownpx skills add fusengine/agents --skill git-flowgit clone --depth 1 https://github.com/fusengine/agentsWrote 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/fusengine/agents/git-flow)<a href="https://agentmods.dev/skills/fusengine/agents/git-flow"><img src="https://agentmods.dev/badge/skills/fusengine/agents/git-flow.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.00020 | $0.02502 |
| Opus 5 | $0.00010 | $0.01251 |
| Sonnet 5 | $0.00004 | $0.00500 |
| Haiku 4.5 | $0.00002 | $0.00250 |
Grade A, and why
git-flow 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.
How it starts
The opening of the file, as written. The whole thing — 162 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Git Flow Best Practices (2026)
Workflow Choice
| Strategy | When | Verdict |
|---|---|---|
| Trunk-based (direct main) | Solo dev, prototypes, strong CI | OK if you have automated tests |
| GitHub Flow (feature branch → PR → merge → delete) | Teams, OSS, code review | ✅ Default |
| Git Flow (develop/release/hotfix) | Heavy release cycles | ❌ Outdated for most projects |
fuse-commit-pro default: GitHub Flow.
Branch Naming Convention
Format: <type>/<scope-or-summary> (kebab-case).
| Type | Use | Example |
|---|---|---|
feat/ |
New feature | feat/seo, feat/oauth-google |
fix/ |
Bug fix | fix/sniper-loop, fix/csv-parser |
chore/ |
Maintenance, deps | chore/bump-deps, chore/rename-files |
docs/ |
Documentation | docs/api-reference |
refactor/ |
Refactoring (no behavior change) | refactor/extract-utils |
perf/ |
Performance | perf/db-indexes |
test/ |
Tests only | test/auth-coverage |
ci/ |
CI/CD config | ci/github-actions-cache |
build/ |
Build system | build/vite-config |
style/ |
Formatting | style/prettier-pass |
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 · 162 lines · 20 tokens per session scan A 0f0493b662e6
git-flow is a skill published in the GitHub repository fusengine/agents (25 stars, last pushed today), licensed MIT. It adds 20 tokens to every session and 2,502 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-09-03.
Other skills, from other repositories
radin-record
Log feedback, bugs, follow-ups, or ideas raised mid-session as structured backlog entries, so they survive past the conversation. Use for /radin-record, "log this to the backlog", "add as follow-up/bug/idea", "record what we just found", "note this for later", "add findings to backlog". Triggers even on vague asks…
radin-doctor
Check that radin's own install under /.claude is complete and its optional companion tools are reachable. Use for /radin-doctor, "check my radin install", "is radin installed correctly", "radin doctor", "verify radin install".
designing-interfaces
Creates a design system for software with a UI. Use when a project has a user interface and architecture is confirmed — whether creating from scratch or extracting patterns from existing code.
managing-product
Extracts product requirements and produces a PRD. Use when a user wants to build software and needs to define what to build before architecture or implementation, when scoping an MVP, or when translating a vague idea into a buildable specification.
orchestrating-software-dev
Runs software development projects from idea to completion. Use when starting a software project, adding a feature, fixing a bug, or resuming an in-progress build.
collecting-sources
Collects research sources with quality evaluation. Use when gathering or finding sources, building a source library, searching for academic papers, or performing RADAR assessment.