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/cloudera/minimcp/cursorrulesgit clone --depth 1 https://github.com/cloudera/minimcpWhat 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.00919 | $0.00919 |
| Opus 5 | $0.00460 | $0.00460 |
| Sonnet 5 | $0.00184 | $0.00184 |
| Haiku 4.5 | $0.00092 | $0.00092 |
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.
How it starts
The opening of the file, as written. The whole thing — 86 lines — stays where its author put it; the contents beside it link to each section on GitHub.
General guidelines
Always use Markdown for documentation and README files.
Git
Commits should be of the following format:
<type>(<optional scope>): <description>
[optional body]
- Keep commits small and focused.
- Do not add "Made-with: Cursor".
- Commit messages should explain why its being done, not what its doing.
The type is one of the following:
- feat: A new feature
- fix: A bug fix
- chore: A chore (not user-facing)
- docs: Documentation changes
- refactor: A code refactor
- test: A test change
- perf: A performance improvement
- style: A style change
- build: A build change
- ci: A CI change
Python Code Style & Formatting
- Follow PEP 8 style guidelines.
- Use type hints for all function signatures and class attributes.
- Maximum line length is 120 characters (configured in pyproject.toml via ruff).
- Use
rufffor both linting and formatting. Do not use Black or flake8. - Use
pyrightfor type checking. Do not use mypy. - Prefer explicit imports over wildcard imports (
from x import *). - The project supports Python 3.10+. Do not use syntax or stdlib features that require 3.11 or later without a compatibility shim.
Async
- Use
anyiofor all async primitives:anyio.sleep(),anyio.create_task_group(),anyio.Event(),anyio.CapacityLimiter(), etc. - Never use
asyncio.sleep(),asyncio.create_task(),asyncio.gather(), or otherasyncio-specific APIs directly.
MiniMCP API conventions
- Register tools, prompts, and resources using the decorator interface:
@mcp.tool(),@mcp.prompt(),@mcp.resource(). - All tool/prompt/resource handler functions must have Pydantic-serializable argument and return types (they are validated by
MCPFunc). - To access the active request context inside a handler, use
mcp.context.get(). Never pass context as a function argument. - To send progress notifications from a handler, use
mcp.context.get_responder().report_progress(...). - Use the
ScopeTgeneric parameter when writing transport or MiniMCP subclasses that need custom per-request scope. - Custom exceptions should subclass
MiniMCPError(user-facing) orInternalMCPError(internal-only).
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 · 86 lines · 919 tokens per session scan A b7cb07fa9ca9
cursorrules is a cursor rule published in the GitHub repository cloudera/minimcp (10 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 919 tokens to every session, about $0.0046 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
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.
python_lib
Tips and guidelines specific to the development of the Streamlit Python library, not applicable to scripts and e2e tests.
specs
This directory contains product and tech specs for Streamlit features.