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/mitas/cursor-rules/commit-messagegit clone --depth 1 https://github.com/mitas/cursor-rulesWhat 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.00015 | $0.00777 |
| Opus 5 | $0.00008 | $0.00388 |
| Sonnet 5 | $0.00003 | $0.00155 |
| Haiku 4.5 | $0.00002 | $0.00078 |
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 yesterday.
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 — 91 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Semantic Commit Messages
Context
- Enables standardized, meaningful commit messages across projects.
- Makes commit history more readable and navigable.
- Facilitates automated versioning and changelog generation.
- Based on Angular commit conventions.
- Ensures consistency in development workflows.
Critical rules
- Structure commit messages in format:
<type>(<scope>): <subject>. - Type MUST be one of the following:
feat: New features (bumps minor version).fix: Bug fixes (bumps patch version).docs: Documentation changes only.style: Code style changes (formatting, semicolons, etc).refactor: Code changes neither fixing bugs nor adding features.perf: Performance improvements.test: Adding/modifying tests.build: Build system or external dependency changes.ci: CI configuration changes.chore: Regular maintenance tasks.revert: Reverts a previous commit.
- Scope is optional and indicates section of codebase (e.g., component name, module).
- Use
cursorscope (e.g.,chore(cursor)) when adding or modifying Cursor rules.
- Use
- Subject should be imperative, present tense, not capitalized, no period at end.
- All lines MUST be 72 characters or less.
- Header line (type + scope + subject) should ideally be 50 characters or less, otherwise hard-limit is 72 characters.
- For longer messages, add blank line after header followed by body text.
- Body should explain what and why, not how (code explains how).
- In case commit contains multiple changes subjects - add bulleted list of changes within body.
- Footer (optional) for referencing issues:
Closes #123, #456. - Breaking changes must include
BREAKING CHANGE:in footer. - Header, body and footer must be always separated by a blank line.
- Multiple-line commit messages require proper git editor setup or -m flag with quoted text.
- Always output the complete commit message for user review before executing any git commit command.
- For UI display/references only, emojis can be used with types (not in actual commit message):
- ✨
feat- new feature. - 🐛
fix- bug fix. - 📝
docs- documentation. - 🎨
style- code style. - ♻️
refactor- code refactoring. - ⚡️
perf- performance. - ✅
test- testing. - 👷
build- build system. - 💚
ci- continuous integration. - 🧹
chore- maintenance. - ⏪
revert- revert changes.
- ✨
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.
- yesterday First seen · 91 lines · 15 tokens per session scan A 7cb54272743c
commit-message is a cursor rule published in the GitHub repository mitas/cursor-rules (2 stars, last pushed 1y ago), licensed MIT. It adds 15 tokens to every session and 777 once invoked, about $0.0001 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-31.
Other cursor rules, from other repositories
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
typescript
Changes to these high-fan-out internals can affect every message, delta, element, or rerun. Keep work in them minimal, and benchmark changes with representative stress-test apps.
coolify-ai-docs
Master reference to all Coolify AI documentation in .ai/ directory.
python_lib
Tips and guidelines specific to the development of the Streamlit Python library, not applicable to scripts and e2e tests.
specs
This directory contains product and tech specs for Streamlit features.