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/cohen-liel/hivemind/git-workflownpx skills add cohen-liel/hivemind --skill git-workflowgit clone --depth 1 https://github.com/cohen-liel/hivemindWrote 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/cohen-liel/hivemind/git-workflow)<a href="https://agentmods.dev/skills/cohen-liel/hivemind/git-workflow"><img src="https://agentmods.dev/badge/skills/cohen-liel/hivemind/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.00027 | $0.00789 |
| Opus 5 | $0.00014 | $0.00394 |
| Sonnet 5 | $0.00005 | $0.00158 |
| Haiku 4.5 | $0.00003 | $0.00079 |
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 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 — 132 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Git Workflow Patterns
Commit Message Format (Conventional Commits)
<type>(<scope>): <short summary>
[optional body: WHY this change was made]
[optional footer: BREAKING CHANGE, closes #issue]
Types:
feat: New featurefix: Bug fixrefactor: Code change that doesn't add features or fix bugstest: Adding or updating testsdocs: Documentation onlychore: Build, deps, config changesperf: Performance improvementci: CI/CD changes
Examples:
feat(auth): add JWT refresh token rotation
Implement sliding refresh tokens to improve security.
Old refresh tokens are invalidated immediately on use.
Closes #123
---
fix(api): return 404 when user not found instead of 500
The get_user endpoint was crashing when user_id didn't exist
because db.get() returns None and we were accessing None.email.
---
refactor(models): extract TimestampMixin from all models
All models had duplicate created_at/updated_at columns.
Extracted to reusable mixin to DRY the code.
Branch Strategy (GitHub Flow — simple)
main # Always deployable
feature/ # New features
fix/ # Bug fixes
chore/ # Maintenance
# Never commit directly to main
# Every change = branch → PR → review → merge
Commands
# Start new feature
git checkout -b feat/user-authentication
# Stage only relevant files (never git add .)
git add src/auth.py src/models/user.py tests/test_auth.py
# Amend last commit (before push)
git commit --amend --no-edit
# Interactive rebase to clean up commits
git rebase -i HEAD~3
# Squash all feature commits before merge
git merge --squash feat/user-authentication
# Undo last commit but keep changes
git reset --soft HEAD~1
# See what changed in last commit
git diff HEAD~1 HEAD --stat
# Find when a bug was introduced
git bisect start
git bisect bad # current commit has bug
git bisect good v1.0.0 # known good commit
.gitignore (Python project)
__pycache__/
*.pyc
.env
.env.local
*.egg-info/
dist/
build/
.venv/
venv/
.pytest_cache/
.coverage
htmlcov/
*.log
.DS_Store
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 · 132 lines · 27 tokens per session scan A 2b7b4bc09afc
git-workflow is a skill published in the GitHub repository cohen-liel/hivemind (108 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 27 tokens to every session and 789 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
rulesync
Generates and syncs AI rule configuration files (.cursorrules, CLAUDE.md, copilot-instructions.md) across 20+ coding tools from a single source. Use when syncing AI rules, running rulesync commands, importing or generating rule files, or managing shared AI coding configurations.
establishing-project-context
Use when the user asks to establish shared project language, or project work exposes a conflicting, renamed, or deprecated domain term that needs active semantic modeling. Routine small tasks stay on the fast path.
autoprompt
Explicit-only useful-first orchestration. Invoke /autoprompt to turn a mission into one executable roadmap, build dependency-safe lanes, and verify the result with independent reviewers. Never infer invocation from ordinary requests. Never resume from leftover artifacts without an explicit resume instruction.
loongsuite-pilot-insight
基于 LoongSuite Pilot / AI Coding Agent 日志生成事件洞察、组织洞察、数据质量、研发效能和 AI Native 使用类 SLS 报表时使用；包含 AI Coding 事件表语义，以及团队报表可选的部门维表、deptuser 组织关系、指标口径和公共 CTE，通常与 sls-dashboard-builder 一起使用。.
map-fast
Minimal workflow for small, low-risk changes — no planning, no learning.
alipay-webhooks
Receive and verify Alipay (Antom / Alipay+) webhook notifications. Use when setting up Alipay webhook handlers, debugging RSA256 Signature header verification, or handling payment events like notifyPayment, notifyCapture, notifyRefund, notifyAuthorization, and notifyDispute.