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 rules/mrostamii/rancher-mcp-server/git-commit-messagesgit clone --depth 1 https://github.com/mrostamii/rancher-mcp-serverWhat 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.00477 | $0.00477 |
| Opus 5 | $0.00238 | $0.00238 |
| Sonnet 5 | $0.00095 | $0.00095 |
| Haiku 4.5 | $0.00048 | $0.00048 |
Grade A, and why
git-commit-messages 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 3d 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 Commit Messages
Use the Conventional Commits specification for every commit message in this project.
Format
<type>[optional scope]: <description>
[optional body]
[optional footer(s)]
Types
- feat: New feature (MINOR in SemVer)
- fix: Bug fix (PATCH in SemVer)
- BREAKING CHANGE or type!: Breaking API change (MAJOR in SemVer)
- Other allowed types:
build:,chore:,ci:,docs:,style:,refactor:,perf:,test:
Release automation
This project uses release-please. Commit types control what happens:
feat:→ triggers a minor release (0.6.0 → 0.7.0)fix:→ triggers a patch release (0.6.0 → 0.6.1)feat!:/BREAKING CHANGE:→ triggers a major release (0.6.0 → 1.0.0)chore:,docs:,ci:, etc. → included in changelog but do not trigger a release on their own
Choose the commit type carefully — it determines whether a release PR is opened.
Rules
- Prefix with a type followed by colon and space
- Scope is optional, in parentheses after type (e.g.
feat(parser):) - Description is a short summary right after the colon
- Body and footers follow after a blank line
- For breaking changes: use
BREAKING CHANGE:in the footer or append!after type/scope
Examples
feat(harvester): add VM list tool
fix(steve): handle pagination for large collections
docs: update API client rules in cursorrules
feat(config)!: require cluster in all tool params
BREAKING CHANGE: cluster is now required for kubernetes_* and harvester_* tools.
When suggesting or editing commit messages, always use this format.
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.
- 3d ago First seen · 67 lines · 477 tokens per session scan A ddcac0be8efc
git-commit-messages is a cursor rule published in the GitHub repository mrostamii/rancher-mcp-server (12 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 477 tokens to every session, about $0.0024 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 cursor rules, from other repositories
git-commit-attribution
Git commits must use the human developer identity only; never Cursor Agent co-authorship.
git-conventional-commits
Conventional commit messages and logical multi-commit workflow when working with Git.
dos-verify-done-claims-cursorrules-prompt-file
Gate AI done/shipped/fixed claims on ground truth from the DOS kernel (dos verify, dos commit-audit) — git ancestry and the commit's own diff, never the agent's own narration.
pause
Checkpoint the session into git so it survives a close and resumes from any device. Use on "pause", "checkpoint", "cache this session", "save my place", or "I'm stepping away" — writes a handoff, commits work in flight, and pushes.
no-cursor-commit-attribution
Never add Cursor co-author or attribution trailers to git commits or PRs.
git-commits
description: "Reference and apply the git commits skill for Conventional Commit formatting and pre-push checks." alwaysApply: true.