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/cosmicstack-labs/mercury-agent-skills/git-workflownpx skills add cosmicstack-labs/mercury-agent-skills --skill git-workflowgit clone --depth 1 https://github.com/cosmicstack-labs/mercury-agent-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/cosmicstack-labs/mercury-agent-skills/git-workflow)<a href="https://agentmods.dev/skills/cosmicstack-labs/mercury-agent-skills/git-workflow"><img src="https://agentmods.dev/badge/skills/cosmicstack-labs/mercury-agent-skills/git-workflow.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.00018 | $0.01598 |
| Opus 5 | $0.00009 | $0.00799 |
| Sonnet 5 | $0.00004 | $0.00320 |
| Haiku 4.5 | $0.00002 | $0.00160 |
Grade A, and why
git-workflow 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 5d 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 — 194 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Git Workflow
Master the fundamentals of version control collaboration — from branching strategy to commit hygiene to review culture.
Core Principles
1. Commits Are Communication
Every commit message is a message to your future self and your teammates. Write for the reader who needs to understand why a change was made, not just what changed.
2. Branch Intentionally
Your branching strategy should match your team size, release cadence, and deployment model. The best strategy is the one your team actually follows consistently.
3. Review With Empathy
Code review is a conversation, not an inspection. The goal is shared understanding and improved quality, not catching mistakes.
4. Rebase Thoughtfully
History matters. Clean history helps debugging and release management. But never rebase shared branches without team coordination.
Git Workflow Maturity Model
| Level | Branching | Commits | Reviews | CI |
|---|---|---|---|---|
| 1: Ad-hoc | All on main | "Update" messages | None | None |
| 2: Basic | Feature branches | Some context in messages | Occasional | Lint checks |
| 3: Standard | Trunk-based or GitFlow | Conventional commits | Required PRs | Full test suite |
| 4: Advanced | Short-lived branches | Atomic, rebased commits | Automated + manual | Deploy previews |
| 5: Elite | Feature flags on trunk | Semantic versioning from commits | Async + sync pairing | Auto-deploy to prod |
Target: Level 3+ for team projects. Level 4+ for high-velocity teams.
Actionable Guidance
Branching Strategies
Trunk-Based Development (Recommended for most teams)
- Main branch: Always deployable. Protected — no direct pushes.
- Feature branches: Short-lived (1-2 days max). Branch from main, merge back to main.
- Release branches: Cut from main at release time. Bug fixes cherry-picked.
main: o---o---o---o---o---o---o
\ /
feature-A: o---o---o
\
feature-B: o---o
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.
- 5d ago First seen · 194 lines · 18 tokens per session scan A bed2d4924ed0
git-workflow is a skill published in the GitHub repository cosmicstack-labs/mercury-agent-skills (471 stars, last pushed 10d ago), licensed MIT. It adds 18 tokens to every session and 1,598 once invoked, about $0.0001 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-30.
Other skills, from other repositories
git-workflow-and-versioning
Structures git workflow practices. Use when making any code change. Use when committing, branching, resolving conflicts, opening or reviewing a pull request (PR), pushing to a remote, or when you need to organize work across multiple parallel streams. Use when cutting a release, choosing a semantic version bump…
chinese-commit-conventions
中文 commit 与 changelog 配置参考——Conventional Commits 中文适配、commitlint/husky/commitizen 中文模板、conventional-changelog 中文配置。仅在用户显式 /chinese-commit-conventions 时调用，不要根据上下文自动触发。.
comet-safe-delivery
在保护无关脏改动、关联 worktree、子模块和用户明确边界的前提下，提交、推送、合并或完成范围明确的 Comet 变更。用户要求提交、推送、合并回目标分支、清理 worktree 或交付已准备好的改动时使用。.
ac-commit-manager
Manage git commits for autonomous coding. Use when committing feature implementations, creating descriptive commits, managing git workflow, or handling version control.
update-skills-from-changelog
Update ElevenLabs agent skills from a merged weekly changelog in elevenlabs-dx, then open a pull request in elevenlabs/skills. Trigger after a changelog merges to main on elevenlabs-dx, or when asked to update skills from changelog YYYY-MM-DD.
agent-commit
Analyze changes and create a meaningful commit with agent authorship. Internal skill for evolveloop.