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/benwilcock/rhdh-labWrote 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/benwilcock/rhdh-lab/git-github)<a href="https://agentmods.dev/rules/benwilcock/rhdh-lab/git-github"><img src="https://agentmods.dev/badge/rules/benwilcock/rhdh-lab/git-github/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/benwilcock/rhdh-lab/git-github"><img src="https://agentmods.dev/badge/rules/benwilcock/rhdh-lab/git-github.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.00571 | $0.00571 |
| Opus 5.5 | $0.00228 | $0.00228 |
| Sonnet 5.5 | $0.00114 | $0.00114 |
| Haiku 4.5 | $0.00057 | $0.00057 |
Grade A, and why
git-github 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.
How it starts
The opening of the file, as written. The whole thing — 57 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Git & GitHub Conventions
Commit Messages
Write clear, detailed commit messages that explain why the change was made, not just what changed.
Format
<short summary in imperative mood, max ~72 chars>
<optional body: explain motivation, context, trade-offs, or anything
non-obvious about the change. Wrap lines at ~72 chars.>
Guidelines
- Use imperative mood: "Add feature" not "Added feature" or "Adds feature"
- First line is a concise summary; add a blank line then a body for anything non-trivial
- Reference related docs or issues when relevant (e.g. "See docs/architecture.md")
- Group related changes into a single commit; separate unrelated changes into distinct commits
Email & Identity
This repository uses a GitHub noreply email to keep the author's personal email private.
- NEVER change
user.emailin git config - NEVER use a personal email address in commits
- The repo-level config is already set; do not override it
Secret Safety
Before every commit:
- Run
git diff --stagedand review for secrets, credentials, personal paths, or tokens - NEVER commit files matching:
.env,*-credentials.yaml,*.pem,*.key - NEVER commit hardcoded passwords, API keys, tokens, or personal absolute paths (e.g.
/Users/...,/home/...) - Use
${ENV_VAR}references for all secrets; set real values only in the gitignored.env - If in doubt, check
.gitignorecovers the file before staging
Submodule: rhdh-local
rhdh-local/is a git submodule tracking the upstream RHDH Local projectmodified: rhdh-local (untracked content)ingit statusis normal -- do not try to fix it- NEVER stage or commit changes inside
rhdh-local/ - To update the submodule:
cd rhdh-local && git checkout main && git pull origin main && cd ..then commit the new SHA in rhdh-lab
Force Push
- NEVER force push to
mainunless the user explicitly requests it - When rewriting history (e.g. email changes, squashing), always use
--force-with-leasefirst; only fall back to--forceif lease fails due to the rewrite itself
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 · 57 lines · 571 tokens per session scan A 0f624496d9c0
git-github is a cursor rule published in the GitHub repository benwilcock/rhdh-lab (2 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 571 tokens to every session, about $0.0023 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.