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/iSerter/laravel-claude-agentsWrote 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/iserter/laravel-claude-agents/conventional-commits)<a href="https://agentmods.dev/rules/iserter/laravel-claude-agents/conventional-commits"><img src="https://agentmods.dev/badge/rules/iserter/laravel-claude-agents/conventional-commits/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/iserter/laravel-claude-agents/conventional-commits"><img src="https://agentmods.dev/badge/rules/iserter/laravel-claude-agents/conventional-commits.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.00431 | $0.00431 |
| Opus 5.5 | $0.00172 | $0.00172 |
| Sonnet 5.5 | $0.00086 | $0.00086 |
| Haiku 4.5 | $0.00043 | $0.00043 |
Grade A, and why
conventional-commits 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 2mo 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
Use Conventional Commits for every commit message.
Format
<type>[optional scope]: <description>
[optional body]
[optional footer]
- First line: type (required), optional scope in parentheses, colon and space, short description in imperative mood (lowercase, no period).
- Body (optional): wrap at 72 chars; explain what and why, not how.
- Footer (optional): e.g.
BREAKING CHANGE:,Refs #123.
Types
| Type | Use for |
|---|---|
feat |
New feature (MINOR bump) |
fix |
Bug fix (PATCH bump) |
docs |
Documentation only |
style |
Formatting, whitespace, no code change |
refactor |
Code change that is not a fix or feature |
perf |
Performance improvement |
test |
Adding or updating tests |
build |
Build system, dependencies, tooling |
ci |
CI configuration |
chore |
Other changes (e.g. repo maintenance) |
revert |
Revert a previous commit |
Examples
feat(api): add pagination to skills list
fix(auth): resolve token expiry race condition
docs: update README installation steps
chore(deps): bump composer dependencies
feat(parser)!: drop support for PHP 7.4
BREAKING CHANGE: PHP 8.0+ is now required.
Rules
- Use imperative mood: "add feature" not "added feature" or "adds feature".
- No period at the end of the subject line.
- For breaking changes, use
!after type/scope and/or aBREAKING CHANGE:footer. - When suggesting or writing commits, always use this format.
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.
- 2mo ago First seen · 58 lines · 431 tokens per session scan A ef1bd6de38a7
conventional-commits is a cursor rule published in the GitHub repository iSerter/laravel-claude-agents (48 stars, last pushed 6mo ago), licensed MIT. It adds 431 tokens to every session, about $0.0017 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-30.
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.
commits
Conventional Commits standards for clear, semantic commit messages.
no-ai-contributors
Never add AI tools as git authors or project contributors.
conventional-commits
Use the Conventional Commit Messages specification to generate commit messages.
git-discipline
Commit, push, and branching rules. Owns ALL git behavior; other files state only their deviations.