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/vypdev/copilotWrote 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/vypdev/copilot/commit-messages)<a href="https://agentmods.dev/rules/vypdev/copilot/commit-messages"><img src="https://agentmods.dev/badge/rules/vypdev/copilot/commit-messages/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/vypdev/copilot/commit-messages"><img src="https://agentmods.dev/badge/rules/vypdev/copilot/commit-messages.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.00278 | $0.00278 |
| Opus 5.5 | $0.00111 | $0.00111 |
| Sonnet 5.5 | $0.00056 | $0.00056 |
| Haiku 4.5 | $0.00028 | $0.00028 |
Grade A, and why
commit-messages 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.
What it actually says
Commit messages
The commit message must use the current branch name as prefix, with any / replaced by -.
Format
<normalized-branch>: <short description>
[optional body]
- Prefix: current branch name, replacing
/with-. Example: branchfeature/292-github-action-rename→ prefixfeature-292-github-action-rename. - Description: imperative, lowercase, no trailing period. You may optionally include conventional type (
feat,fix,docs, etc.) in the description.
Examples
Branch feature-292-github-action-rename:
feature-292-github-action-rename: add concurrency and permissions to ci_checkfeature-292-github-action-rename: fix docs callouts (Info instead of Note/Tip)
Branch fix/123-docs-anchor (normalized to fix-123-docs-anchor):
fix-123-docs-anchor: remove invalid MDX heading anchors
When suggesting or writing a commit message, use the current branch with / replaced by - as the prefix. If you don't know the branch, tell the user to use their branch name as the prefix.
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 · 33 lines · 278 tokens per session scan A 5b909a062f90
commit-messages is a cursor rule published in the GitHub repository vypdev/copilot (3 stars, last pushed today), licensed MIT. It adds 278 tokens to every session, about $0.0011 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-31.
Other cursor rules, from other repositories
commit
Commit, stage, or record changes in the working tree with one Conventional Commits message. Use when the user asks to commit or stage changes.
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.