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/squirrelogic/mcp-feature-discussion/conventional-commitsgit clone --depth 1 https://github.com/squirrelogic/mcp-feature-discussionWrote 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/squirrelogic/mcp-feature-discussion/conventional-commits)<a href="https://agentmods.dev/rules/squirrelogic/mcp-feature-discussion/conventional-commits"><img src="https://agentmods.dev/badge/rules/squirrelogic/mcp-feature-discussion/conventional-commits.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.1 | $0.00007 | $0.01058 |
| Opus 5 | $0.00003 | $0.00529 |
| Sonnet 5 | $0.00001 | $0.00212 |
| Haiku 4.5 | $0.00001 | $0.00106 |
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 5d 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 conventional-commits — 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 — 146 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Conventional Commits Rule
Description
This rule defines the format and structure for commit messages following the Conventional Commits 1.0.0 specification. It ensures consistent, semantic, and machine-readable commit messages.
Rule Type
workflow
Rule Format
{
"type": "workflow",
"name": "conventional_commits",
"description": "Enforces Conventional Commits 1.0.0 specification",
"filters": [
{
"type": "event",
"pattern": "pre_commit"
}
],
"steps": [
{
"action": "validate",
"description": "Validate commit message format",
"requirements": [
"Message MUST be prefixed with a type",
"Type MUST be one of: feat, fix, docs, style, refactor, perf, test, build, ci, chore",
"Scope is OPTIONAL and MUST be in parentheses",
"Description MUST immediately follow the colon and space",
"Description MUST use imperative mood ('add' not 'added')",
"Description MUST be less than 100 characters",
"Breaking changes MUST be indicated by '!' or 'BREAKING CHANGE:' footer",
"Body MUST be separated from description by one blank line",
"Footer MUST be separated from body by one blank line"
]
},
{
"action": "execute",
"description": "Format and create commit",
"script": {
"detect_type": {
"feat": ["add", "create", "implement", "introduce"],
"fix": ["fix", "correct", "resolve", "patch"],
"docs": ["document", "comment", "update.*docs"],
"style": ["style", "format", "lint"],
"refactor": ["refactor", "restructure", "reorganize"],
"perf": ["optimize", "performance", "improve.*speed"],
"test": ["test", "spec", "coverage"],
"build": ["build", "dependency", "package"],
"ci": ["ci", "pipeline", "workflow"],
"chore": ["chore", "misc", "task"]
},
"format_message": {
"template": "${type}${scope}: ${description}\n\n${body}\n\n${footer}",
"variables": {
"type": "Detected from changes or user input",
"scope": "Optional, derived from file paths",
"description": "First line of commit message",
"body": "Detailed explanation of changes",
"footer": "Optional references or breaking changes"
}
},
"command": [
"# Extract type from changes or prompt user",
"TYPE=$(detect_change_type \"$CHANGES\" || prompt_user \"Enter commit type:\")",
"",
"# Extract scope from file paths",
"SCOPE=$(get_common_path \"$CHANGED_FILES\")",
"",
"# Format the commit message",
"printf \"%s\\n\\n%s\\n\\n%s\" \"$TYPE${SCOPE:+($SCOPE)}: $DESCRIPTION\" \"$BODY\" \"$FOOTER\" > \"$COMMIT_MSG_FILE\""
]
}
}
]
}
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.
- 5d ago First seen · 146 lines · 7 tokens per session scan A ca2ca7c68218
conventional-commits is a cursor rule published in the GitHub repository squirrelogic/mcp-feature-discussion (1 stars, last pushed 1y ago), licensed MIT. It adds 7 tokens to every session and 1,058 once invoked, about $0.0000 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to conventional-commits, differing in 0 lines, and is treated as a copy.
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.
git_workflow
Git Workflow and Configuration for AGB SDK.
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.