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 commands/christopherlouet/claude-base/ops-gitflowgit clone --depth 1 https://github.com/christopherlouet/claude-baseWrote 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/commands/christopherlouet/claude-base/ops-gitflow)<a href="https://agentmods.dev/commands/christopherlouet/claude-base/ops-gitflow"><img src="https://agentmods.dev/badge/commands/christopherlouet/claude-base/ops-gitflow.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.00000 | $0.00855 |
| Opus 5 | $0.00000 | $0.00428 |
| Sonnet 5 | $0.00000 | $0.00171 |
| Haiku 4.5 | $0.00000 | $0.00085 |
Grade A, and why
ops-gitflow 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 — 83 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GITFLOW Agent
Manage the GitFlow branching model: init, feature, release and hotfix branches.
Request context
$ARGUMENTS
Goal
Drive a GitFlow workflow on the repository — initialise the model, then manage feature, release and hotfix branches with the correct merges, tags and back-merges.
GitFlow is mutually exclusive with the foundation's default trunk-ish flow (
feature/offmain, rebase, squash — see.claude/rules/git.md). Use this opt-in module only on projects that have chosen GitFlow.
Usage
/ops:ops-gitflow <init|feature|release|hotfix> [action] [name|version]
Dispatch on the first argument (the sub-command); the second is the action
(start / finish / list / …). Check prerequisites (git repo, clean tree,
up-to-date branches) before every operation.
init
- Check prerequisites (git repo, current branch, uncommitted changes).
- Create the
developbranch frommainif it does not exist, push it to the remote. - Recommend branch protection for
mainanddevelop. - Output: configured branches (
main= production,develop= integration), prefixes (feature/,release/,hotfix/), the table of sub-commands, and the recommended workflow (feature → develop → release → main).
feature — actions: start | finish | list | publish | pull
- start: create
feature/xxxfrom an up-to-datedevelop, push the branch. - finish: merge
--no-ffintodevelop, delete the local and remote branch. - list: list ongoing feature branches.
- publish: push the feature branch to the remote.
- pull: fetch a remote feature branch.
- Use kebab-case for branch naming.
release — actions: start | finish | list
- start: create
release/vX.Y.Zfromdevelop, push the branch. - finish: merge into
main, create the tag, back-merge intodevelop, delete the branch. - list: list release branches and existing tags.
- Follow semantic versioning (MAJOR.MINOR.PATCH). Preparation checklist: bump version, changelog, tests. No new features on a release branch.
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 · 83 lines · 0 tokens per session scan A 57b299297fd8
ops-gitflow is a command published in the GitHub repository christopherlouet/claude-base (5 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 855 tokens. 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 commands, from other repositories
release-update
(dev-only) release-update maintainer harness — Claude Code upstream change tracker (release-notes version-delta sweep + docs sync). NOT distributed to user projects.
release
(dev-only) release maintainer harness — MoAI-ADK production release (Enhanced GitHub Flow, scripts/release.sh + GoReleaser). NOT distributed to user projects.
changelog
Generate a changelog entry from git commits since the last tag using conventional commit format.
launch
Preview the public launch — the file bundle, the secret/PII scan, and the release gates — in dry-run mode, cut a release by deriving its version and composing its changelog, and scaffold the changelog-driven release gate into a managed repo. The preview performs zero writes; ship writes the dated CHANGELOG heading and…
release-manager
Automated release coordination and deployment with ruv-swarm orchestration for seamless version management, testing, and deployment across multiple packages.
release-swarm
Orchestrate complex software releases using AI swarms that handle everything from changelog generation to multi-platform deployment.