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/pblagoje/mcp-ollama-pythonWrote 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/pblagoje/mcp-ollama-python/230-review_for_enhancements)<a href="https://agentmods.dev/rules/pblagoje/mcp-ollama-python/230-review_for_enhancements"><img src="https://agentmods.dev/badge/rules/pblagoje/mcp-ollama-python/230-review_for_enhancements/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/pblagoje/mcp-ollama-python/230-review_for_enhancements"><img src="https://agentmods.dev/badge/rules/pblagoje/mcp-ollama-python/230-review_for_enhancements.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.00231 | $0.00231 |
| Opus 5 | $0.00115 | $0.00115 |
| Sonnet 5 | $0.00046 | $0.00046 |
| Haiku 4.5 | $0.00023 | $0.00023 |
Grade A, and why
230-review_for_enhancements 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 9d 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
030 — Review for enhancements before return
After any code change, and before the final reply to the user:
- Review only the code you touched (and thin wrappers you added) for clear improvements.
- Apply improvements when they are local, low-risk, and clearly better:
- Remove duplication introduced by the change
- Tighten names, types, and docstrings to match behavior
- Prefer existing project helpers over one-off copies
- Reduce noise (redundant checks, dead code you added)
- Align with nearby style and patterns in the same module
- Do not expand into drive-by refactors of unrelated files or speculative redesigns.
- Do not add features, abstractions, or tests the user did not ask for unless needed to keep the change correct/safe.
- If a larger enhancement is worth doing later, mention it briefly; do not implement it in the same pass unless it is a small fix-up of the current change.
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.
- 9d ago First seen · 20 lines · 231 tokens per session scan A 8958cc6f697c
230-review_for_enhancements is a cursor rule published in the GitHub repository pblagoje/mcp-ollama-python (5 stars, last pushed 18d ago), licensed MIT. It adds 231 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
frontend-architecture
Cursor rule "frontend-architecture" from tomasz-tomczyk/crit, covering frontend architecture, two-paradigm page fork, module pattern, shared modules (used by both modes) and code-review modules (used only by code-review mode).
frontend-css
Cursor rule "frontend-css" from tomasz-tomczyk/crit, covering css rules, responsive & touch and selectors.
review-pr-against-issue
Workflow for reviewing a PR against the GitHub issue it claims to fix, including fetching PRs when gh CLI can't reach github.com.
grug-brained-dev_avoid-abstractions
Don't create abstractions until you have multiple concrete examples.
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.