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/openjkai/secscan_mcpWrote 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/openjkai/secscan_mcp/git-commits)<a href="https://agentmods.dev/rules/openjkai/secscan_mcp/git-commits"><img src="https://agentmods.dev/badge/rules/openjkai/secscan_mcp/git-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/openjkai/secscan_mcp/git-commits"><img src="https://agentmods.dev/badge/rules/openjkai/secscan_mcp/git-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.00292 | $0.00292 |
| Opus 5.5 | $0.00117 | $0.00117 |
| Sonnet 5.5 | $0.00058 | $0.00058 |
| Haiku 4.5 | $0.00029 | $0.00029 |
Grade A, and why
git-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 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.
What it actually says
Git commits
When to commit
- Only create a git commit when the user explicitly asks
- If unclear, ask first — do not commit proactively
Safety
- NEVER update git config
- NEVER run destructive git commands (
push --force,hard reset, etc.) unless explicitly requested - NEVER skip hooks (
--no-verify) unless explicitly requested - NEVER force-push to
main/master— warn the user if they request it - Avoid
git commit --amendunless all apply: user requested amend, HEAD commit is yours this session, not pushed - Do not commit:
.env,*.pem,*.key,credentials.json,.scan-output/, real secrets in fixtures
Commit workflow (when user asks)
- Parallel:
git status,git diff,git log(recent messages for style) - Draft a 1–2 sentence message focused on why
- Stage relevant files, commit with HEREDOC message, verify with
git status - Do not push unless the user asks
Message format
Short imperative summary (50 chars or less if possible)
Optional body: why this change matters.
Example: Add gitleaks adapter with normalized secret findings
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 · 38 lines · 292 tokens per session scan A 39a83a9e75c3
git-commits is a cursor rule published in the GitHub repository openjkai/secscan_mcp (0 stars, last pushed 2mo ago), licensed MIT. It adds 292 tokens to every session, about $0.0012 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-31.
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.