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/heavyblotto/caelusWrote 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/heavyblotto/caelus/git-workflow)<a href="https://agentmods.dev/rules/heavyblotto/caelus/git-workflow"><img src="https://agentmods.dev/badge/rules/heavyblotto/caelus/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/heavyblotto/caelus/git-workflow"><img src="https://agentmods.dev/badge/rules/heavyblotto/caelus/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.00275 | $0.00275 |
| Opus 5.5 | $0.00110 | $0.00110 |
| Sonnet 5.5 | $0.00055 | $0.00055 |
| Haiku 4.5 | $0.00028 | $0.00028 |
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.
What it actually says
Git workflow (Caelus)
dev is the canonical work branch. main is release-only and is promoted by
the maintainer.
Rules
- Commit and push work to
dev. Nothing else by default. - NEVER commit, push, reset, or force-push to
main. The maintainer promotesdev→main, or explicitly tells you to. "Promote" / "release" =main; only then touchmain, and confirm first. - Do NOT create feature branches and do NOT open pull requests unless the maintainer explicitly asks for one.
- Before every
git push, verify the current branch isdev(or a branch the maintainer named this session). If it ismain, stop. - A local
pre-pushhook blocks pushes tomain. Do not bypass it. Promotion is the maintainer's call:CAELUS_ALLOW_MAIN_PUSH=1 git push origin main.
When unsure
Ask before any action that changes branch structure (new branches, PRs,
merges, resets, pushes to main). Match the existing workflow rather than
introducing a new one.
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 · 29 lines · 275 tokens per session scan A 3f0eadcdd183
git-workflow is a cursor rule published in the GitHub repository heavyblotto/caelus (1 stars, last pushed 12d ago), licensed MIT. It adds 275 tokens to every session, about $0.0011 per session on Opus 5.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 cursor rules, from other repositories
rebase-only-merged-agents
When rebasing after a merge, only rebase the agents whose branches you just merged. Do not rebase agents that are still running.
iris
GitHub operations specialist — branches, pull requests, issues, releases, tags. Called by zeus after review. Never pushes or merges without explicit human approval. Integrates with VS Code GitHub Pull Requests extension.
git-workflow
Rules for git operations, commit strategy, and GitHub CLI usage.
release-checklist
What to update with each code change or version release.
git-workflow
Git commit format and PR process - conventional commits.
branching-merging-strategy
This is a set of instructions to the AI Assistant for branching and merging strategy.