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/dryvist/claude-code-plugins/git-flow-nextnpx skills add dryvist/claude-code-plugins --skill git-flow-nextgit clone --depth 1 https://github.com/dryvist/claude-code-pluginsWhat 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.00056 | $0.01163 |
| Opus 5 | $0.00028 | $0.00581 |
| Sonnet 5 | $0.00011 | $0.00233 |
| Haiku 4.5 | $0.00006 | $0.00116 |
Grade A, and why
git-flow-next 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 2d 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 — 98 lines — stays where its author put it; the contents beside it link to each section on GitHub.
git-flow-next Usage Guide
Use this skill when working on repositories configured for the Git Flow branching model.
1. Detect Adoption First
Before any branch, PR, or release work, check the repo's remote default branch:
gh repo view --json defaultBranchRef --jq '.defaultBranchRef.name'
- If default branch is
develop-> Follow this skill. - If default branch is
main-> Use trunk flow (squash-to-main directly). Do NOT follow this skill. - Never infer adoption from the current local branch name.
2. The Branching Model
| Branch | Role | Gets changes by |
|---|---|---|
main |
Production. Protected; no direct pushes. | Merge commits only — squash and rebase are banned. |
develop |
Default integration branch. Protected; no direct pushes. | Squash-merged feature PRs (default); merge commits for back-merges. |
feature/<issue>-<sid8>-<slug> |
Topic work | Branched from fresh develop. |
release/<version> |
Release stabilization | Branched from develop; merge-committed to main; back-merged to develop. |
hotfix/<slug> |
Production fix | Branched from main; PR to main (merge commit); back-merged to develop. |
3. Dedicated Worktree Setup
All feature development happens in dedicated worktrees. Branch names carry the
session id: <issue>-<sid8>-<slug>, where <sid8> is the first 8 hex chars of
the session/conversation id (generate openssl rand -hex 4 if the runtime has
none). Issueless work drops the issue segment: <sid8>-<slug>. The worktree
directory matches the branch's name segment. Unique-per-session names make
worktree/branch collisions between concurrent sessions structurally
impossible; refs dryvist/ai-assistant-instructions#749.
To prevent wrong nesting:
-
Resolve the destination path using an absolute anchor and create the branch directly in the worktree:
name="123-03a3a401-fix-inventory-loader" git worktree add -b "feature/$name" \ "$(dirname "$(git rev-parse --git-common-dir)")/.worktrees/$name" origin/develop
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.
- 2d ago First seen · 98 lines · 56 tokens per session scan A a0522bc39999
git-flow-next is a skill published in the GitHub repository dryvist/claude-code-plugins (3 stars, last pushed 2d ago), licensed Apache-2.0. It adds 56 tokens to every session and 1,163 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
git-wrapup
Land working-tree changes as logical commits — the work grouped by concern, topped by a release commit (version bump, changelog, regenerated artifacts) and an annotated tag. Verify, commit, tag. Stops at "committed and tagged locally" — no push, no publish. The release-and-publish skill picks up from here. Distilled…
ship
Commit, push, create PR, then after approval check CI and merge. Use when work is done and ready to ship.
git-flow-pr
Executes the full PR-driven development workflow: create an isolated feature branch from the current work, commit all staged changes, rebase cleanly onto the selected base branch (skipping any ancestor commits already merged), push the branch, and open a GitHub pull request linked to a related issue. Includes guidance…
git-conventions
Branch naming, commit message format, PR workflow, worktree conventions, versioning policy.
git-guardar
Spec versión: vitals/specs/project-version.md.
git-ops
Git + worktree orchestrator: status survey, per-worktree triage, commits, PRs, branches, releases, rebases — reads inline, writes to a background agent. Triggers on: git status, anything to commit, anything to push, commit, push, create PR, rebase, release, tag, changelog, worktree, land worktrees.