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 mgiovani/cc-arsenal --skill gitflowgit clone --depth 1 https://github.com/mgiovani/cc-arsenalWrote 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/mgiovani/cc-arsenal/gitflow)<a href="https://agentmods.dev/skills/mgiovani/cc-arsenal/gitflow"><img src="https://agentmods.dev/badge/skills/mgiovani/cc-arsenal/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/mgiovani/cc-arsenal/gitflow"><img src="https://agentmods.dev/badge/skills/mgiovani/cc-arsenal/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.00204 | $0.01443 |
| Opus 5.5 | $0.00082 | $0.00577 |
| Sonnet 5.5 | $0.00041 | $0.00289 |
| Haiku 4.5 | $0.00020 | $0.00144 |
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 22d 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 — 76 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Gitflow
This skill covers the full gitflow branching model with two long-lived branches and short-lived branches off them.
mainis production. Merging tomaintriggers your deploy pipeline. Treat every merge tomainas a production deploy that your users will see shortly after.dev(sometimes calleddevelop) is the integration branch. Day-to-day feature and fix work lands here first.- Short-lived branches:
feat/<desc>andfix/<desc>offdev,release/<x.y.z>offdev,hotfix/<x.y.z>offmain.
Pick the flow
Read the matching reference in full and follow it step by step. Each one is self-contained.
| The user wants to... | Flow | Read |
|---|---|---|
Ship the accumulated dev work to production |
Release | references/release.md |
| Get an urgent fix into production now, can't wait for a release | Hotfix | references/hotfix.md |
| Build a new feature or a fix that will ride the next release | Feature | references/feature.md |
If the intent is ambiguous (e.g. "ship the settings fix"), ask one question: is this urgent enough to go straight to production (hotfix), or does it ride the next release (feature now, release later)? Then stop and wait for the answer. Don't pick a flow, name a branch, run a command or propose a version until the user replies.
Universal rails
These apply to every flow. They exist because main is live production and a mistake here is user-visible, so the cost of a shortcut is real.
- Requires
gh(brew install gh) for PRs, merges, and releases. Confirmgh auth statussucceeds before the first PR; if not, stop and tell the user to rungh auth login. mainis a deploy button. Never merge tomainwhile any CI check is not green. The full Definition-of-Done gate runs on a PR tomain; wait for all of it. Poll CI every few minutes rather than tight-looping, to keep token cost sane. No CI pipeline configured on the repo? Skip the wait-for-green step and say so explicitly before merging.- Always update
CHANGELOG.mdduring a release and a hotfix (never per-feature; the changelog is assembled at ship time). Seereferences/changelog.mdfor the format. - Conventional Commits. Follow the Conventional Commits spec. Keep commit messages, PR titles, PR bodies, the changelog, and release notes clean and professional.
- Never force-push. Never bypass git hooks (
--no-verifyor equivalent). The pre-push hooks are part of the safety net. If a push fails due to a hook, investigate and root-fix the underlying issue; never bypass. - Stage only the files you intend. Prefer
git add <specific-files>over blanket staging commands. Verify what you are about to stage withgit diff --stagedbefore committing. - Verify before every push. Run
git log --oneline <base>..HEADandgit diff --stat <base>..HEADso you know exactly what is going to the remote, especially before anything that touchesmain. - After any merge to
main(release or hotfix), open a break-glass revert PR and leave it OPEN. It is the one-click rollback. Never merge it yourself. See the shared procedure inreferences/release.md(the revert step is identical for hotfix).
What ships with it
6 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.
- 22d ago Changed · +1 lines 331c062b609f
- 1mo ago Changed · +2 lines 7d5f6da56f69
- 1mo ago Changed · +1 lines 74b36c747a34
- 1mo ago First seen · 72 lines · 204 tokens per session scan A 844fa2ae82ff
gitflow is a skill published in the GitHub repository mgiovani/cc-arsenal (8 stars, last pushed 2d ago), licensed MIT. It adds 204 tokens to every session and 1,443 once invoked, about $0.0008 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
codew-release-qa-sweep
Use before claiming Codewhale release work is done: run the full gate sweep and list the manual QA targets.
release
Skill "release" from Hmbown/Codewhale, covering release, invocation, non-goals and workflow.
github
Drive GitHub via the official gh CLI — repos, issues, pull requests, releases, gists, Actions runs, and raw REST through gh api. Use when the user asks to inspect or manage GitHub.
skillshare-changelog
Generate CHANGELOG.md entry from recent commits in conventional format. Also syncs the website changelog page. Use this skill whenever the user asks to: generate a changelog, document what changed between tags, or create a new CHANGELOG entry. If you see requests like "write the changelog for v0.17", "what changed…
commit-pr
Mandatory Codex/Copilot publication adapter for opencode-swarm. Use for every GitHub issue assignment that results in code changes, commits, pushes, draft PRs, PR body edits, PR readying, release notes, or CI closeout. Must be loaded before git push, gh pr create, gh pr edit, or gh pr ready. Routes to the single…
share-a-library
Use when a managed library is ready to publish to GitHub and hand to teammates as an install command. Run the GitHub publishing steps, then return the exact shareable install command.