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/heyAyushh/staccWrote 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/heyayushh/stacc/pr-message-format)<a href="https://agentmods.dev/rules/heyayushh/stacc/pr-message-format"><img src="https://agentmods.dev/badge/rules/heyayushh/stacc/pr-message-format/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/heyayushh/stacc/pr-message-format"><img src="https://agentmods.dev/badge/rules/heyayushh/stacc/pr-message-format.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.00859 | $0.00859 |
| Opus 5.5 | $0.00344 | $0.00344 |
| Sonnet 5.5 | $0.00172 | $0.00172 |
| Haiku 4.5 | $0.00086 | $0.00086 |
Grade A, and why
pr-message-format 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.
This is a copy
100% identical to commit-message-format — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Git Commit Message Format Rules
This rule defines the commit message guidelines that apply to all commits.
Role of this rule
- This rule is a commit message convention based on Conventional Commits.
- While
PrefixandBREAKING CHANGEfollow the Conventional Commits specification, it adds repository-specific guidelines such aslanguage-based language selection and bullet-list bodies. - When reusing this rule in other projects, adjust
languageand the list of prefixes according to each project's policy.
Language
- In this file,
languageis a logical name that represents the language used in commit messages. language = "en"- The summary and body should, in principle, be written in the language specified by
language.
Basic format (required)
<Prefix>: <summary (imperative / concise)>
- Change item 1 (bullet)
- Change item 2 (bullet)
- ...
Refs: #<issue-number> (optional)
BREAKING CHANGE: <description> (optional)
Prefix
Prefix corresponds to the type in Conventional Commits and should be a lowercase English word.
- feat: new feature
- fix: bug fix
- refactor: refactoring (no behavior change)
- perf: performance improvement
- test: tests added/updated
- docs: documentation updates
- build: build/dependency changes
- ci: CI-related changes
- chore: chores (tools, scripts, etc.)
- style: style-only changes (no logic impact)
- revert: revert a previous change
As in Conventional Commits, you may optionally use the <Prefix>(scope): form when needed (e.g. fix(translation): ...).
For details, see the Conventional Commits specification.
Summary (first line)
- Write a concise summary in the language specified by
language; do not add a trailing period. - Briefly express what was changed and, if needed, why.
- Aim for about 50 characters in the summary line.
Message generation principles
- Always inspect the uncommitted diff (
git diff/git diff --cachedetc.) and generate the summary and body based on those changes. - Do not rely only on issue titles or branch names; summarize the actual changes present in the diff.
- When AI or scripts generate commit messages, they should also use the uncommitted diff as input.
- Bots and automation tools must follow this rule and generate messages based on the diff as well.
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 · 103 lines · 859 tokens per session scan A 3e58dc7cb1e8
pr-message-format is a cursor rule published in the GitHub repository heyAyushh/stacc (3 stars, last pushed 26d ago), licensed MIT. It adds 859 tokens to every session, about $0.0034 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to commit-message-format, differing in 0 lines, and is treated as a copy.
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.