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/sandraschi/ocr-mcp/cursorrulesgit clone --depth 1 https://github.com/sandraschi/ocr-mcpWhat 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.00086 | $0.00086 |
| Opus 5 | $0.00043 | $0.00043 |
| Sonnet 5 | $0.00017 | $0.00017 |
| Haiku 4.5 | $0.00009 | $0.00009 |
Grade A, and why
cursorrules 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 yesterday.
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
Session Context (OCR-MCP)
You have access to a FastMCP 3.4+ OCR server with 14 backends for document text extraction.
Before starting work:
- Check registered backends: manage_workflow(operation="list_backends")
- Check server health: get_status(level="basic")
At end of work:
- OCR results are persisted in the job queue for review
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.
- yesterday First seen · 11 lines · 86 tokens per session scan A 18c5cf2feeb0
cursorrules is a cursor rule published in the GitHub repository sandraschi/ocr-mcp (19 stars, last pushed 3d ago), licensed MIT. It adds 86 tokens to every session, about $0.0004 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-30.
Other cursor rules, from other repositories
pi-en
PI Cognitive AI. Trigger: $pi/coding/dev/code/architecture/API/refactor/debug/bug/error/exception/crash/timeout/performance/optimization/test/compile/git/release/verify/review/CR/product/requirements/ops/growth/design/team/support, or deep/2+ failures/looping/stuck/giving-up/retry/nevermind.
testing
Guide for writing pytest unit and integration tests.
ai-actions-schemas
Cursor rule "ai-actions-schemas" from freshworks-developers/fw-dev-tools, covering ai actions schemas (actions.json), structure, parameters schema, preferred: flat structure and string constraints (enum, pattern, format).
tools
(none|read|write|network|exec) and risk (low|medium|high|critical). These drive the permission classifier — be honest.
development-phase
开发阶段：以新代码清晰合理为先，兼容仅在零代价时顺带.
env-access
Supporting rule — STRICT block on .env access (read AND write). Only .env.example is accessible. Backs rule 1 (write allowlist) with a stricter dual-key bypass.