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 skills/mgiovani/cc-arsenal/gitflownpx skills add mgiovani/cc-arsenal --skill gitflowgit clone --depth 1 https://github.com/mgiovani/cc-arsenalWhat 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.00204 | $0.01339 |
| Opus 5 | $0.00102 | $0.00669 |
| Sonnet 5 | $0.00041 | $0.00268 |
| Haiku 4.5 | $0.00020 | $0.00134 |
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 2d 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 — 72 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)?
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.
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.
- 2d ago First seen · 72 lines · 204 tokens per session scan A 844fa2ae82ff
gitflow is a skill published in the GitHub repository mgiovani/cc-arsenal (7 stars, last pushed 2d ago), licensed MIT. It adds 204 tokens to every session and 1,339 once invoked, about $0.0010 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-08-31.
Other skills, from other repositories
architecture-refiner
Facilitate a structured conversation to define architecture principles for a repository. Supports multiple architecture styles: clean architecture (default), hexagonal / ports & adapters, modular monolith, or custom. Produces a formal architecture document that the corresponding atom will use. Use when setting up a…
lattice-init
Guided setup and upgrade-check experience for Lattice projects -- scans the repository, detects existing configuration and outdated conventions, suggests refiners and available upgrades in priority order, and creates or reconciles the .lattice/ config. Bridges the gap between installing skills and getting first value…
intelligent-investor-graham
Use Graham value investing for Is this investment or speculation, defensive stock screens, margin of safety, Mr. Market, allocation, funds, IPOs.
skill-to-workflow
将现有 Skill、Prompt、SOP 或 Agent 操作说明拆解为可执行、可监控、可重试的 Workflow 规格；识别真实节点、共享子工作流、工具调用、状态、分支、循环、 提示词、数据契约和验收方式。适用于用户要求把一个 Skill 转成工作流、节点图、 编排方案或 Workflow 实现规格时；不替代原 Skill 执行业务任务，也不在未要求时 绑定具体工作流平台或直接部署。.
query-loop-implementation
Implement a production-ready LLM query loop / agent loop for AI applications. Use this skill whenever the user wants to add tool calling, ReAct-style reasoning-action-observation cycles, function calling loops, query engines, agent runtimes, toolresult feedback, max-turn exits, or Claude Code-like Agent Loop behavior…
cncf-landscape
Use this skill when discovering and comparing cloud-native technologies from the CNCF Landscape for an architecture or engineering decision. Query the live public Landscape API, filter candidates by capability, category, maturity, license, and repository signals, then produce an evidence-backed shortlist with…