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/jmenzies722/shua-labsWrote 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/jmenzies722/shua-labs/live-vs-git)<a href="https://agentmods.dev/rules/jmenzies722/shua-labs/live-vs-git"><img src="https://agentmods.dev/badge/rules/jmenzies722/shua-labs/live-vs-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/jmenzies722/shua-labs/live-vs-git"><img src="https://agentmods.dev/badge/rules/jmenzies722/shua-labs/live-vs-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.00075 | $0.00075 |
| Opus 5.5 | $0.00030 | $0.00030 |
| Sonnet 5.5 | $0.00015 | $0.00015 |
| Haiku 4.5 | $0.00007 | $0.00007 |
Grade A, and why
live-vs-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 2mo 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
The live studio tree may lag git. Prefer a PR to master.
- Do not start a new Vercel project to "fix" the split.
- Do not invent a second public site.
- GitHub is the bus. Update
HANDOFF.mdand the PR.
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.
- 2mo ago First seen · 11 lines · 75 tokens per session scan A 2171e17fb063
live-vs-git is a cursor rule published in the GitHub repository jmenzies722/shua-labs (1 stars, last pushed 2mo ago), licensed MIT. It adds 75 tokens to every session, about $0.0003 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
branching-strategy
GitFlow-inspired branching strategy for this project. Solo development omits the develop branch.
commit
Conventional Commits specification and git commit workflow rules.
git
Git identity and commits — canonical text is root AGENTS.md.
maidan-claimant
Take coding work from a Maidan queue as a session claimant (claim a task routed to sessions, do it here, run the pre-push gate, hand the change back so Maidan opens the draft pull request, report usage, start review, release). Use when asked to take, claim or work Maidan tasks, or to follow up on a Maidan pull request…
git-flow
Branching, commits and PR hygiene. Always applies.
git-conventions
Git workflow and commit conventions for AI-assisted development.