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/cam-douglas/agent-instructionsWrote 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/cam-douglas/agent-instructions/git-privacy-and-secrets)<a href="https://agentmods.dev/rules/cam-douglas/agent-instructions/git-privacy-and-secrets"><img src="https://agentmods.dev/badge/rules/cam-douglas/agent-instructions/git-privacy-and-secrets/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/cam-douglas/agent-instructions/git-privacy-and-secrets"><img src="https://agentmods.dev/badge/rules/cam-douglas/agent-instructions/git-privacy-and-secrets.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.00194 | $0.00194 |
| Opus 5.5 | $0.00078 | $0.00078 |
| Sonnet 5.5 | $0.00039 | $0.00039 |
| Haiku 4.5 | $0.00019 | $0.00019 |
Grade C, and why
git-privacy-and-secrets scanned grade C with 1 finding 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.
Reaches for credential fileshighPrivilege escalation
SSH keys, cloud credentials, git-credentials, .npmrc, /etc/shadow: reading these is how a config file becomes a credential leak.
Never stage, commit, or push secrets, credentials, passwords, tokens, private keys, `.env*` (except `.env.example`), `.netrc`, `.npmrc`, `.pypirc`, or credential JSON. Do not use `--no-verify`. If a hook denies the actio What it actually says
Never run git commit, merge, rebase, cherry-pick, pull-with-merge, annotated tag, or notes with a private inbox. Always set GIT_AUTHOR_* and GIT_COMMITTER_* to Cursor Agent <[email protected]> or use git -c [email protected]. A *@users.noreply.github.com address is also allowed. Never run git config to change identity.
Never stage, commit, or push secrets, credentials, passwords, tokens, private keys, .env* (except .env.example), .netrc, .npmrc, .pypirc, or credential JSON. Do not use --no-verify. If a hook denies the action, stop. Follow /skills/git-safety/SKILL.md.
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 · 9 lines · 194 tokens per session scan C 96417bc70a45
git-privacy-and-secrets is a cursor rule published in the GitHub repository cam-douglas/agent-instructions (2 stars, last pushed 1mo ago), licensed MIT. It adds 194 tokens to every session, about $0.0008 per session on Opus 5.5. A static security scan graded it C with 1 finding (reaches for credential files). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-19.
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.