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/cmnemoi/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/cmnemoi/cursor-rules/005-commit-conventions)<a href="https://agentmods.dev/rules/cmnemoi/cursor-rules/005-commit-conventions"><img src="https://agentmods.dev/badge/rules/cmnemoi/cursor-rules/005-commit-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/cmnemoi/cursor-rules/005-commit-conventions"><img src="https://agentmods.dev/badge/rules/cmnemoi/cursor-rules/005-commit-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.00000 | $0.00591 |
| Opus 5.5 | $0.00000 | $0.00236 |
| Sonnet 5.5 | $0.00000 | $0.00118 |
| Haiku 4.5 | $0.00000 | $0.00059 |
Grade A, and why
005-commit-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.
How it starts
The opening of the file, as written. The whole thing — 95 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Commit Message Conventions
1.0.0
Context
- These rules apply to all commit messages in the project
- They ensure a clear and searchable commit history
- They facilitate automated changelog generation
- They promote consistency across the development team
Requirements
Commit Structure
- Use the Conventional Commits format:
<type>(<scope>): <description> - Keep the first line under 72 characters
- Write description in imperative, present tense (e.g., "add" not "added")
- Use the body to explain what and why, not how
- Reference issues and pull requests at the end of the body
Commit Types
feat: A new featurefix: A bug fixdocs: Documentation changesstyle: Changes that don't affect code functionality (formatting, etc.)refactor: Code changes that neither fix bugs nor add featuresperf: Performance improvementstest: Adding or correcting testschore: Changes to build process, dependencies, etc.
Commit Scope
- Use scope to indicate the component affected (e.g.,
auth,api,ui) - Keep scope names consistent across commits
- Use lowercase for scope names
- Omit scope for changes that affect multiple components
Breaking Changes
- Mark breaking changes with
!after type/scope:feat(api)!: change authentication API - Include
BREAKING CHANGE:in the commit body with explanation - Provide migration instructions when possible
Language Standards
- Write all commit messages in English
- Use clear and concise language
- Avoid technical jargon unless necessary
- Be specific about what changed
Examples
feat(auth): implement JWT authentication
- Add JWT token generation and validation
- Create authentication middleware
- Update user repository to support token storage
Closes #123
feat(api)!: change response format to follow JSON:API spec
BREAKING CHANGE: API responses now follow the JSON:API specification. All response objects are now wrapped in a data property and include type and id fields.
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 · 95 lines · 591 tokens per session scan A a1cc094e2e09
005-commit-conventions is a cursor rule published in the GitHub repository cmnemoi/cursor-rules (2 stars, last pushed 1y ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 591 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-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.
git-commit-standards
Enforce structured Git commit messages.
conventional-commits
Use the Conventional Commit Messages specification to generate commit messages.