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 hughedward/gitflow-skills --skill gitflowgit clone --depth 1 https://github.com/hughedward/gitflow-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/hughedward/gitflow-skills/gitflow)<a href="https://agentmods.dev/skills/hughedward/gitflow-skills/gitflow"><img src="https://agentmods.dev/badge/skills/hughedward/gitflow-skills/gitflow/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/hughedward/gitflow-skills/gitflow"><img src="https://agentmods.dev/badge/skills/hughedward/gitflow-skills/gitflow.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.00025 | $0.02894 |
| Opus 5.5 | $0.00010 | $0.01158 |
| Sonnet 5.5 | $0.00005 | $0.00579 |
| Haiku 4.5 | $0.00003 | $0.00289 |
Grade A, and why
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 1mo 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 — 350 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Git Flow
Note on Branch Names: Examples use default Git Flow naming (
main,develop,feature/*,release/*,hotfix/*). If your.gitflowconfig uses custom names (e.g.,devinstead ofdevelop), substitute accordingly.
Philosophy: Branching Model, NOT a Tool
Git Flow is a branching strategy protocol - a set of conventions for how to organize your branches. It is NOT dependent on any specific tool.
┌─────────────────────────────────────────────────────────┐
│ Git Flow 理念 → 用原生 git实现 ✓ │
│ Git Flow 工具 → 可选，非必须 (optional) │
└─────────────────────────────────────────────────────────┘
Core Branch Structure
| Branch | Purpose | Lifetime |
|---|---|---|
main/master |
Production-ready code | Indefinite |
develop |
Integration branch for features | Indefinite |
feature/* |
Develop new features | Short-term |
release/* |
Prepare production release | Short-term |
hotfix/* |
Fix critical production bugs | Short-term |
Why Pure Git?
The git-flow-avh CLI tool is just a wrapper around native git commands. Understanding the underlying git commands gives you:
- No dependencies - works anywhere git is installed
- Full control - understand and customize each operation
- Debugging - know exactly what's happening
- Portability - not tied to a specific tool
Quick Start
For new repository setup: See "Initialize Repository" below
For daily workflow: Use the workflow decision tree to determine which operation to perform
Workflow Decision Tree
Need to work on Git Flow repository?
│
├─ New feature? → Feature Workflow
├─ Prepare release? → Release Workflow
├─ Fix production bug? → Hotfix Workflow
└─ New repository? → Initialize Repository
Initialize Repository
Set up a new repository with Git Flow branches:
Pure Git Method (Recommended)
# 1. Ensure you're on main/master
git checkout main
# 2. Create develop branch from main
git checkout -b develop
# 3. Push both branches to remote
git push -u origin main
git push -u origin develop
What ships with it
5 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 1mo ago First seen · 350 lines · 25 tokens per session scan A e5b6ed782f3d
gitflow is a skill published in the GitHub repository hughedward/gitflow-skills (6 stars, last pushed 7mo ago), licensed MIT. It adds 25 tokens to every session and 2,894 once invoked, about $0.0001 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
release
Generic release assistant — analyzes repo release rules, caches them in .omc/RELEASERULE.md, then guides the release.
ship
Ship workflow: detect + merge base branch, run tests, review diff, bump VERSION, update CHANGELOG, commit, push, create PR. Use when asked to "ship", "deploy", "push to main", "create a PR", "merge and push", or "get it deployed". Proactively invoke this skill (do NOT push/PR directly) when the user says code is…
publish
Publish oh-my-opencode to npm by triggering the GitHub Actions publish workflow and verifying its artifacts. Ship-only: never runs pre-publish-review or re-reviews merged code unless the user explicitly asks. Argument: . Triggers: publish, release, deploy, npm publish.
pre-publish-review
Nuclear-grade 12-agent pre-publish release gate. Runs /get-unpublished-changes to detect all changes since last npm release, spawns up to 10 ultrabrain agents for deep per-change analysis, invokes /review-work (orchestrator manual QA plus one gate reviewer) for holistic review, and 1 oracle for overall release…
release
CONTRIBUTOR TOOL - Cut a plugin release: bump plugin.json version, finalize CHANGELOG, update README if needed, gate on make ci, commit, tag vX.Y.Z, and create the GitHub release. Use when shipping a new plugin version. NOT distributed.
get-unpublished-changes
Compare HEAD with the latest published npm versions and list all unpublished changes by release layer. Triggers: unpublished changes, changelog, what changed, whats new.