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/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/git-commit-workflow)<a href="https://agentmods.dev/rules/squirrelogic/mcp-feature-discussion/git-commit-workflow"><img src="https://agentmods.dev/badge/rules/squirrelogic/mcp-feature-discussion/git-commit-workflow/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/squirrelogic/mcp-feature-discussion/git-commit-workflow"><img src="https://agentmods.dev/badge/rules/squirrelogic/mcp-feature-discussion/git-commit-workflow.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.00012 | $0.00939 |
| Opus 5.5 | $0.00005 | $0.00376 |
| Sonnet 5.5 | $0.00002 | $0.00188 |
| Haiku 4.5 | $0.00001 | $0.00094 |
Grade A, and why
git-commit-workflow 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.
This is a copy
100% identical to git-commit-workflow — 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 — 160 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Git Commit Workflow Rule
Description
This rule defines the complete workflow for validating changes, running tests, and creating commits. It ensures that all changes are properly tested and validated before being committed using the conventional commits format.
Rule Type
workflow
Rule Format
{
"type": "workflow",
"name": "git_commit_workflow",
"description": "Validates changes and creates conventional commits",
"filters": [
{
"type": "event",
"pattern": "pre_commit"
}
],
"steps": [
{
"action": "validate",
"description": "Run tests and type checks",
"requirements": [
"All tests MUST pass",
"TypeScript compilation MUST succeed",
"Build process MUST complete successfully"
]
},
{
"action": "execute",
"description": "Validate and commit changes",
"script": {
"steps": [
{
"name": "run_tests",
"command": "npm test",
"on_failure": "abort"
},
{
"name": "type_check",
"command": "npm run type-check",
"on_failure": "abort"
},
{
"name": "build",
"command": "npm run build",
"on_failure": "abort"
},
{
"name": "check_changes",
"command": "git status --porcelain",
"store_output": "CHANGED_FILES"
},
{
"name": "stage_changes",
"command": "git add ."
},
{
"name": "create_commit",
"use_rule": "conventional-commits"
}
]
}
}
]
}
Workflow Steps
-
Run Tests
- Execute the test suite using
npm test - Abort if any tests fail
- Ensure all new features have corresponding tests
- Execute the test suite using
-
Type Checking
- Run TypeScript type checking
- Verify no type errors exist
- Abort if type checking fails
-
Build Process
- Run the build process
- Ensure the project builds successfully
- Abort if build fails
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 · 160 lines · 12 tokens per session scan A 49e946a3c629
git-commit-workflow is a cursor rule published in the GitHub repository squirrelogic/mcp-feature-discussion (1 stars, last pushed 1y ago), licensed MIT. It adds 12 tokens to every session and 939 once invoked, about $0.0000 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to git-commit-workflow, 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.
no-ai-contributors
Never add AI tools as git authors or project contributors.
commits
Conventional Commits standards for clear, semantic commit messages.
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.
git-commit-standards
Enforce structured Git commit messages.