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/j4flmao/agent-skillsWrote 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/j4flmao/agent-skills/commit-standards)<a href="https://agentmods.dev/rules/j4flmao/agent-skills/commit-standards"><img src="https://agentmods.dev/badge/rules/j4flmao/agent-skills/commit-standards/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/j4flmao/agent-skills/commit-standards"><img src="https://agentmods.dev/badge/rules/j4flmao/agent-skills/commit-standards.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.00017 | $0.00336 |
| Opus 5 | $0.00009 | $0.00168 |
| Sonnet 5 | $0.00003 | $0.00067 |
| Haiku 4.5 | $0.00002 | $0.00034 |
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.
What it actually says
Git Commit Standards
Cursor/AI MUST follow these rules when writing git commit messages.
1. Conventional Commits format
Every commit message must adhere to the Conventional Commits specification.
Format: <type>(<scope>): <subject>
Allowed Types:
feat: A new featurefix: A bug fixdocs: Documentation only changes (e.g., Markdown files inskills/)style: Changes that do not affect the meaning of the code (white-space, formatting)refactor: A code change that neither fixes a bug nor adds a featureperf: A code change that improves performancetest: Adding missing tests or correcting existing testschore: Changes to the build process or auxiliary tools and libraries
2. Subject Line Rules
- Use the imperative, present tense: "change" not "changed" nor "changes".
- Do NOT capitalize the first letter.
- Do NOT place a period
.at the end. - Keep it under 50 characters.
3. Body Rules (Optional but highly recommended)
- If the change is complex, leave a blank line after the subject and write a detailed body.
- Explain what and why, not how (the code explains how).
Example:
feat(enterprise): add release trains skill documentation
This standardizes the release schedule across all R&D departments,
preventing feature-driven deployment delays.
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 · 41 lines · 17 tokens per session scan A 395d51a3eae5
commit-standards is a cursor rule published in the GitHub repository j4flmao/agent-skills (22 stars, last pushed 2d ago), licensed MIT. It adds 17 tokens to every session and 336 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-09-05.
Other cursor rules, from other repositories
git
Conventional commit message format for git commits.
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.
conventional-commits
Use the Conventional Commit Messages specification to generate commit messages.
git-commits
description: "Reference and apply the git commits skill for Conventional Commit formatting and pre-push checks." alwaysApply: true.
git-commit-standards
Enforce structured Git commit messages.