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/henriquemoody/charlie/dir.commit-messagesgit clone --depth 1 https://github.com/henriquemoody/charlieWrote 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/henriquemoody/charlie/dir.commit-messages)<a href="https://agentmods.dev/rules/henriquemoody/charlie/dir.commit-messages"><img src="https://agentmods.dev/badge/rules/henriquemoody/charlie/dir.commit-messages.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.00175 | $0.00175 |
| Opus 5 | $0.00088 | $0.00088 |
| Sonnet 5 | $0.00035 | $0.00035 |
| Haiku 4.5 | $0.00017 | $0.00017 |
Grade A, and why
dir.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 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
Conventional Commits
All commit messages must follow the Conventional Commits format:
<type>(<scope>): <subject>
<body>
<footer>
Types
- feat: New feature
- fix: Bug fix
- docs: Documentation changes
- style: Code style/formatting
- refactor: Code refactoring
- test: Test updates
- chore: Build/tooling changes
Examples
feat(auth): add OAuth2 support
Implement OAuth2 authentication flow using the authorization code grant.
Closes #123
fix(api): handle null response from upstream service
Add null check before processing API response to prevent crashes.
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 · 44 lines · 175 tokens per session scan A fd6fb3ef0fc2
dir.commit-messages is a cursor rule published in the GitHub repository henriquemoody/charlie (6 stars, last pushed 5mo ago), licensed MIT. It adds 175 tokens to every session, about $0.0009 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.
git-conventions
See CONTRIBUTING.md → "PR & commit conventions" for PR title format, commit messages, and branch naming.
git
辅助生成 Git 提交信息和执行 Git 命令.
commit-and-push
Commit (conventional commit) files and push to the remote repository.
commit-sponsors
Every git commit message must acknowledge BetterDesk supporters.
no-tool-contributors
Never add AI coding tools as contributors or co-authors.