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.
git clone --depth 1 https://github.com/platinoff/poolAIWrote 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/rules/platinoff/poolai/git-workflow)<a href="https://agentmods.dev/rules/platinoff/poolai/git-workflow"><img src="https://agentmods.dev/badge/rules/platinoff/poolai/git-workflow/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/rules/platinoff/poolai/git-workflow"><img src="https://agentmods.dev/badge/rules/platinoff/poolai/git-workflow.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.00000 | $0.01352 |
| Opus 5.5 | $0.00000 | $0.00541 |
| Sonnet 5.5 | $0.00000 | $0.00270 |
| Haiku 4.5 | $0.00000 | $0.00135 |
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 1mo 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 — 96 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Git Workflow — Conventional Commits (CL) & Push
⚠️ CRITICAL: MSYS2 bash only
All git commands run in MSYS2 bash (C:\msys64\usr\bin\bash.exe).
Do NOT use PowerShell, cmd, or Cursor integrated terminal for git (CreateFileMapping, index.lock, truncated output). Use external MSYS2 UCRT64 only.
Git order (status → commit → push)
git status --short— check modified/unstaged first.- Read/modify files before
git addif needed (AI: avoid staging files you still need to edit). git add <paths>orgit add -A(use with care).git commit— CL (Conventional Commits) subject + Summary у тілі, якщо в коміті є код (див. нижче).git push— pre-push hook runscargo fmt --all --check; fix format then re-commit if it fails.
Summary у коміті (якщо є зміни коду)
Перед git commit перевір staged diff (git diff --cached --stat).
- Є зміни в
src/,tests/,crates/,Cargo.toml→ commit з обов’язковим тіломSummary:(кілька-mабо HEREDOC): що змінено, якіcargoкоманди прогнані, FM/scope за наявності. - Лише
docs/,.cursor/, README без коду → subject + короткий Summary (рекомендовано). - Шаблон і приклад —
.cursor/commands/git-push.mdп.3a; після push — самарі в чат п.3b.
Commit format (CL = Conventional Commits)
<type>(<scope>): <subject>
[optional body - рекомендується: 2-4 bullet points]
[optional footer]
Types: feat | fix | docs | style | refactor | perf | test | build | ci | chore | revert
Scope examples: vm, ui, raid, network, cloud, ml, docs, scripts, concept
Subject: imperative, lowercase, ~50 chars.
Commit summary/body (2–4 bullets) — обов’язково, якщо коміт містить код (див. вище):
- що саме зроблено (модулі, FM-id)
- які перевірки виконані (
cargo fmt,cargo test-ci, clippy — що реально запускали) - нотатки (features, env, не стаджити
data/audit/*.log.gz)
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.
- 1mo ago First seen · 96 lines · 0 tokens per session scan A f6231994e2d9
git-workflow is a cursor rule published in the GitHub repository platinoff/poolAI (4 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,352 tokens. 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 cursor rules, from other repositories
git
Git workflow — commit format, push policy, and PR process.
commit-sponsors
Every git commit message must acknowledge BetterDesk supporters.
no-ai-contributors
Never add AI tools as git authors or project contributors.
git-discipline
Commit, push, and branching rules. Owns ALL git behavior; other files state only their deviations.
git-commit-standards
Enforce structured Git commit messages.
conventional-commits
Use the Conventional Commit Messages specification to generate commit messages.