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/static-analysis-githooks)<a href="https://agentmods.dev/rules/jterratsdev/ableton-live-mcp/static-analysis-githooks"><img src="https://agentmods.dev/badge/rules/jterratsdev/ableton-live-mcp/static-analysis-githooks/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/static-analysis-githooks"><img src="https://agentmods.dev/badge/rules/jterratsdev/ableton-live-mcp/static-analysis-githooks.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.00433 | $0.00433 |
| Opus 5.5 | $0.00173 | $0.00173 |
| Sonnet 5.5 | $0.00087 | $0.00087 |
| Haiku 4.5 | $0.00043 | $0.00043 |
Grade A, and why
static-analysis-githooks 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
Static Analysis & Git Hooks
Every project must run fast static analysis before commit and deeper analysis in CI. Hooks are guardrails, not replacements for review or tests.
Required Tooling
- TypeScript/JavaScript: TypeScript typecheck, ESLint, Prettier or project formatter, dependency audit, and secret scanning.
- Web/UI: lint accessibility rules where available and keep Playwright smoke checks available for critical flows.
- Python: Ruff, mypy or pyright, Bandit, dependency audit, and formatter when Python code exists.
- Infrastructure: Checkov, tfsec, or equivalent IaC scanner when Terraform, OpenTofu, Bicep, CloudFormation, or Kubernetes manifests exist.
- Security: Semgrep or CodeQL for SAST, plus Trivy or Grype for containers when images are built.
Pre-Commit Hook
- A pre-commit hook is mandatory before any commit.
- The hook must run only fast checks suitable for local feedback: formatting check, lint, typecheck for touched packages when practical, secret scan, and staged-file validation.
- The hook must fail closed. If analysis fails, the commit must not proceed.
- Do not bypass hooks with
--no-verifyunless the user explicitly approves and a follow-up item records the reason. - Hook configuration must be version-controlled and reproducible for every contributor.
Pre-Push / CI
- Slower checks belong in pre-push or CI: full test suite, Playwright E2E, SAST, dependency scan, container scan, IaC scan, and build.
- CI must run at least the same checks as local hooks, plus deeper project-wide checks.
- PRs cannot be approved when static analysis, typecheck, security scan, or required hooks fail.
Evidence
- Developer handoff must include exact static analysis commands run and results.
- CI evidence must link failed checks to logs and responsible owners.
- Any deferred static analysis finding needs severity, owner, rationale, and follow-up backlog item.
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 · 33 lines · 433 tokens per session scan A 16c826f94389
static-analysis-githooks is a cursor rule published in the GitHub repository jterratsdev/ableton-live-mcp (0 stars, last pushed 1mo ago), licensed MIT. It adds 433 tokens to every session, about $0.0017 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.