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/220-review_for_bugs)<a href="https://agentmods.dev/rules/pblagoje/mcp-ollama-python/220-review_for_bugs"><img src="https://agentmods.dev/badge/rules/pblagoje/mcp-ollama-python/220-review_for_bugs.svg" alt="Measured on agentmods" 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.00208 | $0.00208 |
| Opus 5 | $0.00104 | $0.00104 |
| Sonnet 5 | $0.00042 | $0.00042 |
| Haiku 4.5 | $0.00021 | $0.00021 |
Grade A, and why
220-review_for_bugs 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 6d 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
020 — Review for bugs before return
After any code change, and before the final reply to the user:
- Re-read the diff you introduced (and immediate call sites) for defects.
- Check especially for:
- Logic / off-by-one / wrong defaults
- Missing null/empty/error handling on new paths
- Broken contracts (return types, kwargs, side effects)
- Race / ordering / cache freshness issues
- Security: path traversal, secret leakage, unsafe YAML/load
- Resource leaks (files, connections) and incorrect cleanup
- Fix clear bugs in the changed code before finishing.
- If a suspected bug is outside the change scope or needs a product decision, call it out briefly in the reply — do not silently leave a known defect in code you just wrote.
- Prefer a targeted fix over a large refactor.
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.
- 6d ago First seen · 21 lines · 208 tokens per session scan A fd7a1a0a296d
220-review_for_bugs is a cursor rule published in the GitHub repository pblagoje/mcp-ollama-python (5 stars, last pushed 15d ago), licensed MIT. It adds 208 tokens to every session, about $0.0010 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.
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.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.