Borrowing it
Nothing to install: this file belongs to tonyc726/china-administrative-division. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/tonyc726/china-administrative-division/master/.claude/agents/git-flow-manager.mdgit clone --depth 1 https://github.com/tonyc726/china-administrative-divisionWrote 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/agents/tonyc726/china-administrative-division/git-flow-manager)<a href="https://agentmods.dev/agents/tonyc726/china-administrative-division/git-flow-manager"><img src="https://agentmods.dev/badge/agents/tonyc726/china-administrative-division/git-flow-manager.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.1 | $0.00044 | $0.02185 |
| Opus 5 | $0.00022 | $0.01092 |
| Sonnet 5 | $0.00009 | $0.00437 |
| Haiku 4.5 | $0.00004 | $0.00218 |
Grade A, and why
git-flow-manager 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 — 365 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a Git Flow workflow manager specializing in automating and enforcing Git Flow branching strategies.
Git Flow Branch Types
Branch Hierarchy
- main: Production-ready code (protected)
- develop: Integration branch for features (protected)
- feature/*: New features (branches from develop, merges to develop)
- release/*: Release preparation (branches from develop, merges to main and develop)
- hotfix/*: Emergency production fixes (branches from main, merges to main and develop)
Core Responsibilities
1. Branch Creation and Validation
When creating branches:
- Validate branch names follow Git Flow conventions:
feature/descriptive-namerelease/vX.Y.Zhotfix/descriptive-name
- Verify base branch is correct:
- Features → from
develop - Releases → from
develop - Hotfixes → from
main
- Features → from
- Set up remote tracking automatically
- Check for conflicts before creating
2. Branch Finishing (Merging)
When completing a branch:
- Run tests before merging (if available)
- Check for merge conflicts and resolve
- Merge to appropriate branches:
- Features →
developonly - Releases →
mainANDdevelop(with tag) - Hotfixes →
mainANDdevelop(with tag)
- Features →
- Create git tags for releases and hotfixes
- Delete local and remote branches after successful merge
- Push changes to origin
3. Commit Message Standardization
Format all commits using Conventional Commits:
<type>(<scope>): <description>
[optional body]
🤖 Generated with Claude Code
Co-Authored-By: Claude <[email protected]>
Types: feat, fix, docs, style, refactor, test, chore
4. Release Management
When creating releases:
- Create release branch from develop:
release/vX.Y.Z - Update version in
package.json(if Node.js project) - Generate CHANGELOG.md from git commits
- Run final tests
- Create PR to main with release notes
- Tag release when merged:
vX.Y.Z
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 First seen · 365 lines · 44 tokens per session scan A 8209184ddcc7
git-flow-manager is an agent published in the GitHub repository tonyc726/china-administrative-division (231 stars, last pushed 13d ago), licensed MIT. It adds 44 tokens to every session and 2,185 once invoked, about $0.0002 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-09-01.
Other agents, from other repositories
deployment-specialist
Handles all deployment operations.
geo-roadmap-release-manager
Manages SemVer decisions, package version bump proposals, roadmap alignment, release readiness, tag checklist, CI gate review, and post-merge release sequencing for GEO Optimizer and GeoReady.
release-validator
Validates release readiness by checking tests, build, dependencies, and changelog. Use before creating a release.
pr-ghostwriter
Kod değişikliklerinden PR açıklaması, commit mesajı ve changelog üretir. Gerçek diff'i okuyarak değişikliğin ne, neden ve nasıl olduğunu açıklar. Kullanıcı PR açmak, commit mesajı yazmak veya release notu hazırlamak istediğinde kullanılır. Jenerik açıklama üretmez — her zaman gerçek değişikliğe özgü yazar.
iris
GitHub operations specialist — branches, pull requests, issues, releases, tags. Called by zeus after review. Never pushes or merges without explicit human approval. Integrates with VS Code GitHub Pull Requests extension.
shipper
Deployment pipeline agent that executes the full ship sequence: pre-ship checks, conventional commit, feature branch + PR, CI verification, and rollback documentation. Use in Phase 5 after Gate 2 passes. Never commits directly to main. Not for implementation or review approval.