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/zackiles/cursor-configWrote 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/zackiles/cursor-config/create-commit-message)<a href="https://agentmods.dev/rules/zackiles/cursor-config/create-commit-message"><img src="https://agentmods.dev/badge/rules/zackiles/cursor-config/create-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/zackiles/cursor-config/create-commit-message"><img src="https://agentmods.dev/badge/rules/zackiles/cursor-config/create-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.00005 | $0.00863 |
| Opus 5.5 | $0.00002 | $0.00345 |
| Sonnet 5.5 | $0.00001 | $0.00173 |
| Haiku 4.5 | $0.00001 | $0.00086 |
Grade A, and why
create-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 — 114 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Writing Commit Messages With Convention Commit
All commit messages follow Conventional Commits standard when generating or suggesting commit messages.
Format
<type>(<scope>): <description>
- Type: Defines the nature of the change.
- Scope: Prefer domain- or module-level identifiers, not file names. Reflects logical grouping or feature boundary, not precise file paths.
- Description: Written in imperative mood. One sentence.
Types
- feat: A new feature.
- fix: A bug fix.
- docs: Documentation changes only.
- style: Code formatting, no logic change.
- refactor: Code restructuring, no behavior change.
- perf: Performance improvements.
- test: Adding or improving tests.
- chore: Build process, dependencies, or auxiliary tools.
- ci: CI/CD config or script changes.
- build: Affects the build system or external dependencies
Examples
Example A (Change History)
Staged Changes:
- Created a new file named
src/auth/login.ts - Imported
src/auth/login.tsintosrc/users/account.ts - Added a modal component class named 'loginForm'
- Tracked a new test file named
test/login.test.ts - Git dif of the documentation shows a new section named "# Logging In"
Output 1 (GOOD):
feat(users-account): add user authentication
Output 2 (BAD):
// No past tense. No periods at the end of the message. No file names for scope
feat(users-account.ts): added user authentication.
Example B (Change History)
Staged Changes:
- Created validation schema in
src/validation/product-schema.tsusing Zod - Integrated schema into product API endpoint in
src/routes/products.ts - Added unit tests in
test/validation/product-schema.test.ts
Output 4 (GOOD):
feat(product-schema): add zod schema validation for product input
Output 4 (BAD):
// Avoid PascalCase. Avoid file extensions. Avoid stating the file path or using vague verbs.
feat(ProductSchema.ts): created validation for product input
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 · 114 lines · 5 tokens per session scan A 7114a3a95420
create-commit-message is a cursor rule published in the GitHub repository zackiles/cursor-config (17 stars, last pushed 1y ago), licensed MIT. It adds 5 tokens to every session and 863 once invoked, about $0.0000 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-30.
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.
git-commit-standards
Enforce structured Git commit messages.
conventional-commits
Use the Conventional Commit Messages specification to generate commit messages.