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.
npx agentmods add rules/pblagoje/mcp-ollama-python/210-pre-commitgit clone --depth 1 https://github.com/pblagoje/mcp-ollama-pythonWhat 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 | $0.00232 | $0.00232 |
| Opus 5 | $0.00116 | $0.00116 |
| Sonnet 5 | $0.00046 | $0.00046 |
| Haiku 4.5 | $0.00023 | $0.00023 |
Grade A, and why
210-pre-commit 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 2d 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
010 — Pre-commit before return
After any code change in this repo, and before the final reply to the user:
- From the repo root, run:
pre-commit run --all-files - If any hook fails, fix the findings (format, lint, trailing whitespace, etc.).
- Re-run
pre-commit run --all-filesuntil it passes (or until remaining failures need an explicit user decision). - Do not skip hooks with
--no-verify/SKIP=unless the user explicitly asked. - This does not create a git commit — only validates/fixes local files. Commits still require an explicit user request (see
review-before-commit.mdc).
If pre-commit is not installed, say so briefly and install/use the project’s documented path (e.g. poetry run pre-commit / venv) when available.
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.
- 2d ago First seen · 20 lines · 232 tokens per session scan A cb8b0c1e32fe
210-pre-commit is a cursor rule published in the GitHub repository pblagoje/mcp-ollama-python (5 stars, last pushed 10d ago), licensed MIT. It adds 232 tokens to every session, about $0.0012 per session on Opus 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
agents
Единые правила и скиллы проекта (зеркало AGENTS.md).
local-brain-mcp-usage
local memory for AI agents.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
typescript
Changes to these high-fan-out internals can affect every message, delta, element, or rerun. Keep work in them minimal, and benchmark changes with representative stress-test apps.
coolify-ai-docs
Master reference to all Coolify AI documentation in .ai/ directory.