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 dryvist/claude-code-plugins --skill git-flow-nextgit clone --depth 1 https://github.com/dryvist/claude-code-pluginsWrote 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/dryvist/claude-code-plugins/git-flow-next)<a href="https://agentmods.dev/skills/dryvist/claude-code-plugins/git-flow-next"><img src="https://agentmods.dev/badge/skills/dryvist/claude-code-plugins/git-flow-next/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/dryvist/claude-code-plugins/git-flow-next"><img src="https://agentmods.dev/badge/skills/dryvist/claude-code-plugins/git-flow-next.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.00057 | $0.01229 |
| Opus 5.5 | $0.00023 | $0.00492 |
| Sonnet 5.5 | $0.00011 | $0.00246 |
| Haiku 4.5 | $0.00006 | $0.00123 |
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 5d 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 — 103 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 — promotions from develop and hotfix PRs. |
develop |
Default integration branch. Protected; no direct pushes. | Squash-merged feature PRs, the squash-merged release-please PR, and merge-committed PRs from hotfix branches. Never merge main into develop. |
feature/<issue>-<sid8>-<slug> |
Topic work | Branched from fresh develop. |
release/<version> |
Release preparation | Not used in this release-please flow. On push to develop, release-please opens a release-please--* PR there for the version, CHANGELOG, and release notes; squash-merge it before promotion. |
hotfix/<slug> |
Production fix | Branch from main; PR to main with a merge commit; then open a PR from the hotfix branch to develop and merge it with a merge commit. |
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.
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.
- 5d ago Changed · +4 lines · +1 tokens per session 115de487f9b5
- 8d ago Changed · +1 lines e672753906ee
- 25d ago Changed ef0ac277fa4f
- 1mo 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 yesterday), licensed Apache-2.0. It adds 57 tokens to every session and 1,229 once invoked, about $0.0002 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-08-31.
Other skills, from other repositories
core-workflow
Detailed development workflow patterns, checklists, and standards. Auto-loads for complex tasks, planning, debugging, or when explicit patterns are needed. Contains session protocols, git conventions, security checklists, review-based validation, and communication standards.
push-preflight
Secret-scans the commits a git push would send (gitleaks + regex layer; never history), then checks clean tree, forbidden files and fast-forward, with size and open-issue advisories. Refuses on any secret hit, no bypass. Triggers on: push to origin, push to github, push to remote, git push, can we push, safe to push…
git-workflow
Skill "git-workflow" from halflength-ampleness75/claude-code-recipes, covering git workflow, branch naming, rules, conventional commits and format.
commit
Create git commits with user approval and no Claude attribution.
commitkit
Commit this session's changes with Conventional Commits messages derived from the actual diff, then push them to origin. Use when the user asks to commit changes, says "commit this", runs "/commitkit", runs "/commitkit all" to commit every change in the tree, or wants a well-formed commit message written for staged…
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.