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/ckrl/ha-gitopsWrote 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/ckrl/ha-gitops/git-conventions)<a href="https://agentmods.dev/rules/ckrl/ha-gitops/git-conventions"><img src="https://agentmods.dev/badge/rules/ckrl/ha-gitops/git-conventions/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/ckrl/ha-gitops/git-conventions"><img src="https://agentmods.dev/badge/rules/ckrl/ha-gitops/git-conventions.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.00537 | $0.00537 |
| Opus 5.5 | $0.00215 | $0.00215 |
| Sonnet 5.5 | $0.00107 | $0.00107 |
| Haiku 4.5 | $0.00054 | $0.00054 |
Grade A, and why
git-conventions 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 Conventions
- Always run
git statusbefore staging/committing to review changes. - Commit messages MUST be in English.
- Never commit secrets,
.env, tokens, or private keys.
Conventional Commits
- Format:
<type>(optional scope)!: <short, imperative summary> - First line <= 72 chars, no trailing period. Use imperative mood (add, fix, update).
- Common types: feat, fix, docs, style, refactor, perf, test, build, ci, chore, revert.
- Scopes (suggested): api, http, routes, config, data, ent, migrations, redis, cache, auth, docs, deps, infra, docker, k8s, tests, ci.
- Breaking change: add
!after type/scope or aBREAKING CHANGE:footer. - Add an optional body after a blank line to explain what and why (not how).
- Optional footers:
Refs: #123,Co-authored-by: Name <email>.
Examples
feat(api): add /v1/health/check endpointfix(redis): correct TTL parsing for cache keysrefactor(ent): split user repository into separate packageperf(http)!: enable gzip by default for large JSON responses- Body example:
Add rate limiting middleware for write endpoints. This prevents abuse and aligns with SLOs. Refs: #123
Merge Policy
- Use no fast-forward merges (
--no-ff) to preserve branch history. - Provide a concise merge summary (e.g.,
merge(api): add JWT middleware). - Do not
git pullremote changes into a feature branch during merge. Rebase or merge explicitly via PR instead.
Local Commit Message Linting
- Use gitlint (CLI) with the
contrib-title-conventional-commitsrule. - Recommended hook manager: Lefthook. Example hook:
commit-msg: gitlint --msg-filename $1 - Enforce title length (<=72), Conventional type, and English summary.
CI Recommendations
- Run
gitlinton all PR commits (e.g., GitHub Actionjorisroovers/gitlint-action). - Optionally require 1+ approval and green checks before
--no-ffmerge.
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 · 53 lines · 537 tokens per session scan A 39ca84492aab
git-conventions is a cursor rule published in the GitHub repository ckrl/ha-gitops (5 stars, last pushed 5mo ago), licensed MIT. It adds 537 tokens to every session, about $0.0021 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
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.
conventional-commits
Use the Conventional Commit Messages specification to generate commit messages.
git-workflow
Git commit format and PR process - conventional commits.