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/danielvm-git/bigpowersWrote 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/danielvm-git/bigpowers/commit-message)<a href="https://agentmods.dev/rules/danielvm-git/bigpowers/commit-message"><img src="https://agentmods.dev/badge/rules/danielvm-git/bigpowers/commit-message/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/danielvm-git/bigpowers/commit-message"><img src="https://agentmods.dev/badge/rules/danielvm-git/bigpowers/commit-message.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.00068 | $0.01957 |
| Opus 5.5 | $0.00027 | $0.00783 |
| Sonnet 5.5 | $0.00014 | $0.00391 |
| Haiku 4.5 | $0.00007 | $0.00196 |
Grade A, and why
commit-message 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 — 142 lines — stays where its author put it; the contents beside it link to each section on GitHub.
story: e82s02
Commit Message
HARD GATE — HARD GATE — Commits must follow Conventional Commits spec (type(scope): description). Do NOT use vague messages like 'fix' or 'updates.' The message must explain the 'why,' not the 'what.'
Modes
- Default: standard Conventional Commits message
- --fix-type: Forces type=fix. Use when commit type is unambiguous.
What "last chat" means
- Primary source of truth: Read
state.yamlvcs.kind. Git usesgit status,git diff, andgit diff --cached; Jujutsu usesjj status,jj diff, andjj log -r @. Run in the repo root. - Context: use the current conversation to summarize intent and to spot breaking API/behavior changes that diff alone may not show.
- If the user tracks a session baseline (e.g. branch, tag, or
git stash createat start), you maygit diff <baseline>..HEADplus uncommitted diffs; otherwise use only the index and working tree.
Quick workflow
- Inventory — List changed paths; group by feature vs chore vs docs vs test-only.
- Decide commit shape — One atomic commit is ideal. If the diff mixes unrelated concerns, recommend multiple commits (each with its own type/scope) before suggesting one message.
- Classify for semantic release —
fix→ patch,feat→ minor, breaking → major. - Write the message —
type(optional-scope)!: description(see REFERENCE.md). Use!or aBREAKING CHANGE:footer when behavior contracts change. - Note defensive-code categories touched — from CONVENTIONS.md: Rate limit | Retry with backoff | Circuit breaker | Timeout | Graceful degradation
- Note fix-ratio contribution — Each
fix:commit counts towardmetrics.commit_ratio.fixinspecs/state.yaml. Afterrelease-branch,session-staterecalculates the ratio automatically. A high fix rate (>30%) triggers a deploy + smoke-test suggestion. - Deliver — Output:
- Proposed full commit message (title + optional body + footers).
- Release bump this commit would drive:
patch|minor|major|none. - Optional native command: Git
git commit -m; Jujutsujj commit -m. Never omit-mor run destructive commands unless asked.
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 · 142 lines · 68 tokens per session scan A 88eb8aea0718
commit-message is a cursor rule published in the GitHub repository danielvm-git/bigpowers (267 stars, last pushed 27d ago), licensed MIT. It adds 68 tokens to every session and 1,957 once invoked, about $0.0003 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-09-03.
Other cursor rules, from other repositories
git-workflow
Git workflow: commits, branches, PRs, history management.
safeword-pr-readiness
Prepare a pull request for human review and decide whether it may leave Draft. Use when creating or rewriting a PR description, marking a PR ready, responding to review, or checking mergeability.
git-commit-standards
Enforce structured Git commit messages.
git-master
Git operations — clean commits, PR prep, conflict resolution, change summaries.
review-workflow
Review, security, and commit workflow.
check
Analyze staged git changes with archguardian before committing.