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/YUNGC0DE/git-cairnWrote 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/yungc0de/git-cairn/cairn-commit-network)<a href="https://agentmods.dev/rules/yungc0de/git-cairn/cairn-commit-network"><img src="https://agentmods.dev/badge/rules/yungc0de/git-cairn/cairn-commit-network/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/yungc0de/git-cairn/cairn-commit-network"><img src="https://agentmods.dev/badge/rules/yungc0de/git-cairn/cairn-commit-network.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.00188 | $0.00188 |
| Opus 5.5 | $0.00075 | $0.00075 |
| Sonnet 5.5 | $0.00038 | $0.00038 |
| Haiku 4.5 | $0.00019 | $0.00019 |
Grade A, and why
cairn-commit-network 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
Cairn commits from Cursor Agent
Cairn's prepare-commit-msg hook calls claude / cursor-agent for distillation.
The default Cursor Agent sandbox injects HTTP(S)_PROXY to a local seatbelt proxy;
cursor-agent then fails with SSL EPROTO … packet length too long, and the
record collapses to metadata-only.
When running git commit (or any command that triggers cairn hooks) from the
Agent shell:
- Request
required_permissions: ["full_network"]at minimum - Prefer
["all"]if the commit also needs unrestricted git hook filesystem access - Do not commit under the default sandbox — distillation will not reach the API
A normal external terminal is fine; only the Agent sandbox breaks this.
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 · 21 lines · 188 tokens per session scan A f59d92e3329d
cairn-commit-network is a cursor rule published in the GitHub repository YUNGC0DE/git-cairn (2 stars, last pushed 2mo ago), licensed MIT. It adds 188 tokens to every session, about $0.0008 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
auto-build-loop
Autonomous build driver after SDD spec approval: phase-scoped headless build sessions, driver-owned commits, cross-provider review gates, milestone pauses, and fail-closed escalation — under explicit opt-in autonomy profiles.
caliber-pre-commit
Run Caliber sync before git commits to keep agent configs up to date.
commit
Check commit styling guide at @COMMIT.md at / folder to see best styling practice for git commit messages.
fusebase-flow-implementation
Fusebase Flow implementation phase rules. Use when editing source code per a locked spec.
new-project-standard
Local adoption files are authoritative. Remote links are navigation only and must not be fetched or executed at runtime.
git
Cursor rule "git" from duongductrong/antigravity-kit, covering git conventions, commit messages, types, subject rules and examples.