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/camilooscargbaptista/cto-toolkit/git-flownpx skills add camilooscargbaptista/cto-toolkit --skill git-flowgit clone --depth 1 https://github.com/camilooscargbaptista/cto-toolkitWrote 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/camilooscargbaptista/cto-toolkit/git-flow)<a href="https://agentmods.dev/skills/camilooscargbaptista/cto-toolkit/git-flow"><img src="https://agentmods.dev/badge/skills/camilooscargbaptista/cto-toolkit/git-flow.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.00115 | $0.01745 |
| Opus 5 | $0.00057 | $0.00873 |
| Sonnet 5 | $0.00023 | $0.00349 |
| Haiku 4.5 | $0.00012 | $0.00175 |
Grade A, and why
git-flow 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 4d 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 — 240 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Git Workflow & Branching Strategy
Help teams choose and follow the right Git workflow. The best workflow is the one your team actually follows consistently.
Branching Strategies
Git Flow (for versioned releases)
Best for: Products with scheduled releases, mobile apps, products with multiple supported versions.
main ─────────●─────────────────●─────────── (production)
│ │
release/1.0 ──┼──●──●──────────┘
│ │
develop ──────┼──┼──●──●──●──●──●──●──────── (integration)
│ │ │ │
feature/auth ─┘ │ │ │
feature/cart ───────┘ │ │
hotfix/crash ─────────────┘ │
feature/search ────────────────────┘
Branches:
main— Production code. Every commit is a release tag.develop— Integration branch. Features merge here.feature/*— New features. Branch from develop, merge to develop.release/*— Release prep. Branch from develop, merge to main + develop.hotfix/*— Production fixes. Branch from main, merge to main + develop.
GitHub Flow (for continuous deployment)
Best for: SaaS, web apps, teams deploying multiple times per day.
main ──●──●──●──●──●──●──●── (always deployable)
│ │ │
│ │ └── feat/notifications (short-lived)
│ └── fix/login-bug
└── feat/dashboard
Rules:
mainis always deployable- Branch from main for any change
- Open a PR, get review, merge to main
- Deploy after merge (automated)
- No long-lived branches
Trunk-Based Development (for high-performing teams)
Best for: Experienced teams with strong CI, feature flags, and automated testing.
main ──●──●──●──●──●──●──●── (deploy continuously)
│ │
└──┘ (very short-lived branches, <1 day)
Rules:
- Everyone commits to main (or very short branches, <1 day)
- Feature flags for incomplete features
- Requires excellent CI/CD and test coverage
- No long-lived branches ever
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.
- 4d ago First seen · 240 lines · 115 tokens per session scan A 4cdc3bd0d639
git-flow is a skill published in the GitHub repository camilooscargbaptista/cto-toolkit (7 stars, last pushed 5mo ago), licensed MIT. It adds 115 tokens to every session and 1,745 once invoked, about $0.0006 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
git-workflow
Git branching, commit conventions, rebase vs merge, conflict resolution, and release tagging. Use when setting up a git workflow, writing commits, resolving conflicts, or preparing a release.
git-workflow-and-versioning
Git workflow and version control best practices. Use when committing code, creating branches, preparing pull requests, or managing release versioning. Use when structuring commit messages or planning a branching strategy.
conventional-commits
Write well-structured conventional commit messages. Use when committing code changes to ensure consistent, parseable commit history that enables automated changelogs and semantic versioning.
changelog-generator
变更日志生成 - 从Git提交历史自动生成分类的Markdown格式Changelog.
gitlawb
Decentralized git for AI agents and humans. Use when the user wants to create repositories, push code, open pull requests, review and merge PRs, manage issues, create or claim bounties, delegate tasks to other agents, register human-readable names on Base L2, or interact with the gitlawb decentralized git network.…
app-store-changelog-v2
App Store Changelog workflow skill. Use this skill when the user needs Generate user-facing App Store release notes from git history since the last tag and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off.