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/blockmatic/basilicWrote 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/blockmatic/basilic/git)<a href="https://agentmods.dev/rules/blockmatic/basilic/git"><img src="https://agentmods.dev/badge/rules/blockmatic/basilic/git/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/blockmatic/basilic/git"><img src="https://agentmods.dev/badge/rules/blockmatic/basilic/git.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.00051 | $0.00051 |
| Opus 5.5 | $0.00020 | $0.00020 |
| Sonnet 5.5 | $0.00010 | $0.00010 |
| Haiku 4.5 | $0.00005 | $0.00005 |
Grade A, and why
git 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 29d 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
Canonical git identity, Conventional Commits, and publication-playbook paths live in root AGENTS.md. Do not diverge from that 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.
- 29d ago Changed · -4 lines · -135 tokens per session 5345c28132d6
- 1mo ago Changed · +1 tokens per session fd8fda8d0bfb
- 1mo ago Changed · -19 lines · -202 tokens per session 37d869951f36
- 1mo ago First seen · 30 lines · 387 tokens per session scan A c7d548fd4023
git is a cursor rule published in the GitHub repository blockmatic/basilic (90 stars, last pushed yesterday), licensed MIT. It adds 51 tokens to every session, about $0.0002 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
review-scope-overrides
Honor explicitly provided base branches in review artifacts.
git-conventions
Git commit message conventions and PR merge strategy for jentic-one.
project-core
Repository-wide project instructions. Canonical rules are in AGENTS.md.
hatch3r-git-conventions
Conventional Commits type list, subject line rules, breaking-change footer format, branch naming template for type/short-description, and change-size discipline (PR-size ceiling with stacked-change escape hatch).
release-ts-sdk
Release @aptos-labs/ts-sdk or @aptos-labs/confidential-asset — version bump, changelog stamp, release PR, then tag + GitHub Release that triggers NPM publish.
git-interaction
Git workflow, permissions, and all git message standards.