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/jterratsdev/ableton-live-mcpWrote 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/jterratsdev/ableton-live-mcp/git-discipline)<a href="https://agentmods.dev/rules/jterratsdev/ableton-live-mcp/git-discipline"><img src="https://agentmods.dev/badge/rules/jterratsdev/ableton-live-mcp/git-discipline/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/jterratsdev/ableton-live-mcp/git-discipline"><img src="https://agentmods.dev/badge/rules/jterratsdev/ableton-live-mcp/git-discipline.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.00488 | $0.00488 |
| Opus 5.5 | $0.00195 | $0.00195 |
| Sonnet 5.5 | $0.00098 | $0.00098 |
| Haiku 4.5 | $0.00049 | $0.00049 |
Grade A, and why
git-discipline 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 — 40 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Git Discipline
Commits
- Each commit must compile and pass tests. Never commit broken code.
- Ask for a Backlog Item ID before suggesting a commit message.
- Use Conventional Commits with the backlog item as scope:
type(ID): short description(e.g.,feat(SA-42): add profile auto-detection). - Use imperative, lowercase summaries under 72 characters when practical.
- Body: numbered list of changes + a paragraph explaining the value proposition.
- Valid types:
feat,fix,refactor,test,docs,chore,perf,ci,build,style,revert. - Mark breaking changes with
!after the type or scope and include aBREAKING CHANGE:footer. - Do not mix unrelated semantic types in one commit. Split mixed work into separate commits.
Git Hooks
- A version-controlled pre-commit hook must run static analysis before every commit.
- Never bypass hooks with
--no-verifyunless the user explicitly approves and a follow-up item records the reason. - For hook tooling and required checks, see static-analysis-githooks.mdc.
Atomic Changes
- One logical change per commit. Don't mix a bug fix with a refactor with a new feature.
- If a refactor is needed before a feature, commit the refactor first, then the feature.
Branches
- Branch from the latest main/develop. Rebase before opening a PR if your branch is stale.
- Branch names:
type/ID-short-description(e.g.,feat/SA-42-profile-detection).
Pull Requests
- PR title follows the same
type(ID): descriptionformat as commits. - PR body must include: summary (1-3 bullets), test plan, and any manual verification steps.
- Keep PRs small (<400 lines changed). If larger, split into stacked PRs or feature flags.
- PRs must link the backlog item and list any breaking changes, migrations, feature flags, or risk acceptances.
Code Review
- Review your own diff before requesting review. Catch the obvious issues yourself.
- Never approve a PR with unresolved conversations, failing CI, or missing tests.
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 · 40 lines · 488 tokens per session scan A ae94e5c664e2
git-discipline is a cursor rule published in the GitHub repository jterratsdev/ableton-live-mcp (0 stars, last pushed 1mo ago), licensed MIT. It adds 488 tokens to every session, about $0.0020 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.
conventional-commits
Use the Conventional Commit Messages specification to generate commit messages.
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.