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 latestaiagents/agent-skills --skill branch-strategy-advisorgit clone --depth 1 https://github.com/latestaiagents/agent-skillsWrote 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/latestaiagents/agent-skills/branch-strategy-advisor)<a href="https://agentmods.dev/skills/latestaiagents/agent-skills/branch-strategy-advisor"><img src="https://agentmods.dev/badge/skills/latestaiagents/agent-skills/branch-strategy-advisor/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/latestaiagents/agent-skills/branch-strategy-advisor"><img src="https://agentmods.dev/badge/skills/latestaiagents/agent-skills/branch-strategy-advisor.svg" alt="Reviewed on agentmods" width="80" 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.00055 | $0.01699 |
| Opus 5 | $0.00028 | $0.00849 |
| Sonnet 5 | $0.00011 | $0.00340 |
| Haiku 4.5 | $0.00006 | $0.00170 |
Grade A, and why
branch-strategy-advisor 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 11d 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 — 267 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Branch Strategy Advisor
Choose and implement the right branching strategy for your team.
When to Use
- Setting up a new project's branching workflow
- Deciding between GitFlow, trunk-based, or GitHub Flow
- Standardizing branch naming conventions
- Configuring branch protection rules
- Scaling branching for larger teams
Strategy Comparison
| Strategy | Best For | Release Cadence | Team Size |
|---|---|---|---|
| Trunk-Based | Continuous deployment, experienced teams | Daily/hourly | Any |
| GitHub Flow | SaaS products, simple workflow | On-demand | Small-Medium |
| GitFlow | Scheduled releases, multiple versions | Weekly/Monthly | Medium-Large |
Strategy 1: Trunk-Based Development
Best for: Teams with strong CI/CD, continuous deployment, feature flags.
main ─────●─────●─────●─────●─────●─────●───→
\ / \ / \ /
feature-a ●─● ●─● ●─●
(short-lived, merged within 1-2 days)
Rules
mainis always deployable- Feature branches live < 2 days
- Use feature flags for incomplete features
- No long-running branches
Branch Naming
feature/ABC-123-short-description
fix/ABC-456-bug-description
Commands
# Start feature
git checkout -b feature/ABC-123-user-auth main
# Keep updated (daily)
git fetch origin
git rebase origin/main
# Merge (same day or next)
git checkout main
git merge --no-ff feature/ABC-123-user-auth
Strategy 2: GitHub Flow
Best for: SaaS products, web apps with continuous deployment.
main ───────●───────●───────●───────●───────→
\ / \ /
●───● ●───●
feature-branch bugfix-branch
(PR) (PR)
Rules
mainis always deployable- Create branch from
mainfor any change - Open PR for discussion
- Deploy from
mainafter merge
Branch Naming
feature/user-authentication
bugfix/login-redirect-loop
hotfix/security-patch
docs/api-documentation
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.
- 11d ago First seen · 267 lines · 55 tokens per session scan A 3e9ea35b4235
branch-strategy-advisor is a skill published in the GitHub repository latestaiagents/agent-skills (5 stars, last pushed 4mo ago), licensed MIT. It adds 55 tokens to every session and 1,699 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
agentic-jujutsu
Quantum-resistant, self-learning version control for AI agents with ReasoningBank intelligence and multi-agent coordination.
agent-release-swarm
Agent skill for release-swarm - invoke with $agent-release-swarm.
agent-release-manager
Agent skill for release-manager - invoke with $agent-release-manager.
github-automation
GitHub workflow automation, PR management, issue tracking, and code review coordination. Integrates with GitHub Actions and repository management. Use when: PR creation, code review, issue management, release automation, workflow setup. Skip when: local-only changes, non-GitHub repositories.
git-flow-master
End-to-end Git operator for any branching strategy. Auto-detects the project's strategy (solo-main, main+integration, enterprise multi-branch, trunk-based, GitFlow, GitHub Flow, GitLab Flow, SDET integration-trunk for chained test-automation suites) from .git config, branches, and the gitstrategy: block in…
version-bump
Version the Team plugin at land time (DEV-internal, not distributed): decide the SemVer level, compute the next free version against current main, update all six version strings, cut the [Unreleased] changelog body into a dated [X.Y.Z] section, run the land-time consistency assertion, and commit chore(version): X.Y.Z.…