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/mordilion/ai-instructions-and-prompts/commit-standardsgit clone --depth 1 https://github.com/mordilion/ai-instructions-and-promptsWrote 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/mordilion/ai-instructions-and-prompts/commit-standards)<a href="https://agentmods.dev/rules/mordilion/ai-instructions-and-prompts/commit-standards"><img src="https://agentmods.dev/badge/rules/mordilion/ai-instructions-and-prompts/commit-standards.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 | $0.01004 | $0.01004 |
| Opus 5 | $0.00502 | $0.00502 |
| Sonnet 5 | $0.00201 | $0.00201 |
| Haiku 4.5 | $0.00100 | $0.00100 |
Grade A, and why
commit-standards 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 4d 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 — 181 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Commit Message Standards
Reference: Conventional Commits v1.0.0
Format
ALWAYS follow this structure:
<type>[optional scope]: <description>
[optional body]
[optional footer(s)]
Commit Types
| Type | Purpose | Semantic Version |
|---|---|---|
feat |
New feature | MINOR |
fix |
Bug fix | PATCH |
docs |
Documentation only | - |
style |
Formatting, whitespace | - |
refactor |
Code restructuring | - |
perf |
Performance improvement | - |
test |
Add/update tests | - |
build |
Build system, dependencies | - |
ci |
CI configuration | - |
chore |
Maintenance, tooling | - |
revert |
Revert previous commit | - |
Description Rules
ALWAYS: Imperative mood ("add" NOT "added")
ALWAYS: Lowercase start
ALWAYS: No period at end
ALWAYS: Under 72 characters
NEVER: Past tense
NEVER: Capitalize first letter
Examples:
feat(auth): add OAuth 2.0 support
fix(api): handle null response
docs: update installation guide
Scope (Optional)
Format:
type(scope): description
Common scopes: api, auth, db, ui, docs, deps, config
Breaking Changes
ALWAYS: Mark with
!orBREAKING CHANGE:footer
Method 1 (Exclamation):
feat!: remove Node 6 support
Method 2 (Footer):
feat: change API format
BREAKING CHANGE: response structure changed
Body (Optional)
When: Additional context needed
Format: One blank line after description
Body Rules
ALWAYS: Use imperative mood (same as description)
ALWAYS: Write prose paragraphs (2-3 sentences max per paragraph)
ALWAYS: Focus on WHAT and WHY, not detailed HOW
NEVER: Use bullet points, dashes, or numbered lists
NEVER: Use section headers ("Changes:", "Details:", etc.)
NEVER: Include code snippets or file lists
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.
- 4d ago First seen · 181 lines · 1,004 tokens per session scan A 8037dd716719
commit-standards is a cursor rule published in the GitHub repository mordilion/ai-instructions-and-prompts (1 stars, last pushed 1mo ago), licensed MIT. It adds 1,004 tokens to every session, about $0.0050 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
git
Conventional commit message format for git commits.
no-ai-attribution
Never attribute commits, comments, or contributions to AI agents.
git-commit-attribution
Git commits must use the human developer identity only; never Cursor Agent co-authorship.
commit-sponsors
Every git commit message must acknowledge BetterDesk supporters.
git_workflow
Git Workflow and Configuration for AGB SDK.
conventional-commits
Use the Conventional Commit Messages specification to generate commit messages.