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 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/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/fusengine/agents/git-flow"><img src="https://agentmods.dev/badge/skills/fusengine/agents/git-flow.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.00020 | $0.02800 |
| Opus 5.5 | $0.00008 | $0.01120 |
| Sonnet 5.5 | $0.00004 | $0.00560 |
| Haiku 4.5 | $0.00002 | $0.00280 |
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 7d 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 — 172 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.
- 7d ago Changed · +10 lines 78f51806a114
- 1mo ago First seen · 162 lines · 20 tokens per session scan A 0f0493b662e6
git-flow is a skill published in the GitHub repository fusengine/agents (33 stars, last pushed 7d ago), licensed MIT. It adds 20 tokens to every session and 2,800 once invoked, about $0.0001 per session on Opus 5.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-batch
Work backlog tasks via sub-agents, prioritized, one commit each; plans first the entries radin-record flagged as needing a plan. Use for "work through my backlog", or name an epic or task to run only those.
catchup
Summarize and review what changed while you were away. Use after a weekend, vacation, or flight to check missed PRs, git commits, Linear tickets, and meetings — one prioritized brief, not a firehose.
github-activity
Report what happened across GitHub repositories over a time window, read only. Invoke when the user asks what merged, which issues were opened or closed, or what moved between milestones since a date or since the last report, across one or more repositories.
implement-issue
Turn one labelled GitHub issue into one reviewed pull request, or stop with a stated reason. Use for every factory run; the message is a link to the issue.
radin-record
Log bugs, follow-ups, ideas or feedback raised this session as backlog entries that outlive the conversation. Use for /radin-record or any ask to save something for later, even a vague one ("add the findings"): scan the whole session.
radin-do
Record one ad-hoc prompt as a backlog entry, then execute just that task. Use for /radin-do .