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/paulpham157/paul-s-cursor-rules/commit-message-generation-rulegit clone --depth 1 https://github.com/paulpham157/paul-s-cursor-rulesWrote 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/paulpham157/paul-s-cursor-rules/commit-message-generation-rule)<a href="https://agentmods.dev/rules/paulpham157/paul-s-cursor-rules/commit-message-generation-rule"><img src="https://agentmods.dev/badge/rules/paulpham157/paul-s-cursor-rules/commit-message-generation-rule.svg" alt="Measured on agentmods" 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.00343 |
| Opus 5 | $0.00000 | $0.00171 |
| Sonnet 5 | $0.00000 | $0.00069 |
| Haiku 4.5 | $0.00000 | $0.00034 |
Grade A, and why
commit-message-generation-rule 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 2d 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.
Copies of this mod
2 near-identical copies found in the catalogue:
- commit-message-generation-rule — 100% identical, 0 lines differ
- commit-message-generation-rule — 100% identical, 0 lines differ
What it actually says
description: Provides guidelines for generating conventional commit messages based on changes in the codebase. globs: */
Commit Message Guidelines:
- Always suggest a conventional commit message with an optional scope in lowercase. Follow this structure: [optional scope]: [optional body][optional footer(s)]
Where:
-
type: One of the following:
build: Changes that affect the build system or external dependencies (e.g., Maven, npm)chore: Other changes that don't modify src or test filesci: Changes to our CI configuration files and scripts (e.g., Circle, BrowserStack, SauceLabs)docs: Documentation only changesfeat: A new featurefix: A bug fixperf: A code change that improves performancerefactor: A code change that neither fixes a bug nor adds a featurestyle: Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc)test: Adding missing tests or correcting existing tests
-
scope (optional): A noun describing a section of the codebase (e.g.,
fluxcd,deployment). -
description: A brief summary of the change in present tense.
-
body (optional): A more detailed explanation of the change.
-
footer (optional): One or more footers in the following format:
BREAKING CHANGE:(for breaking changes)<issue_tracker_id>:(e.g.,Jira-123: Fixed bug in authentication)
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.
- 2d ago First seen · 32 lines · 343 tokens per session scan A a4624f42ca88
commit-message-generation-rule is a cursor rule published in the GitHub repository paulpham157/paul-s-cursor-rules (27 stars, last pushed 1y ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 343 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-09-03.
Other cursor rules, from other repositories
git-conventional-commit-messages
Cursor rules for Git development with conventional commit messages integration.
python-github-setup-cursorrules-prompt-file
Cursor rules for Python development with GitHub setup integration.
pr-template-cursorrules-prompt-file
Cursor rules for PR development with template integration.
release-commit-analysis-auto
This rule analyzes commits to determine if they should trigger a version bump. It categorizes conventional and non-conventional commits into Features, Bug Fixes, Breaking Changes, Documentation, and Other. It uses intelligent keyword matching for non-conventional commits and analyzes file changes to help categorize…
git-workflow
Git workflow: commits, branches, PRs, history management.
git
Cursor rule "git" from gabornyergesX/cursorrules, covering git version control rules, commit best practices, commit messages, commit frequency and branch management.