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/pandeussilvae/mcp-odoo-pandaWrote 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/pandeussilvae/mcp-odoo-panda/mcp-server-rules)<a href="https://agentmods.dev/rules/pandeussilvae/mcp-odoo-panda/mcp-server-rules"><img src="https://agentmods.dev/badge/rules/pandeussilvae/mcp-odoo-panda/mcp-server-rules.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.00000 | $0.01821 |
| Opus 5 | $0.00000 | $0.00911 |
| Sonnet 5 | $0.00000 | $0.00364 |
| Haiku 4.5 | $0.00000 | $0.00182 |
Grade A, and why
mcp-server-rules 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 8d 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.
How it starts
The opening of the file, as written. The whole thing — 315 lines — stays where its author put it; the contents beside it link to each section on GitHub.
MCP Server Implementation Rules
Core Architecture Rules
-
Server Base Class
- All MCP servers must inherit from the base
Serverclass - Must implement all abstract methods defined in the base class
- Must provide proper initialization with server name and version
- Must maintain protocol version compatibility
- Must follow MCP's client-server architecture where:
- MCP Hosts: Programs that want to access data through MCP
- MCP Clients: Protocol clients that maintain 1:1 connections with servers
- MCP Servers: Lightweight programs exposing specific capabilities
- Local Data Sources: Computer's files, databases, and services
- Remote Services: External systems available over the internet
- All MCP servers must inherit from the base
-
Protocol Support
- Must support at least one of the following protocols:
- Stdio Protocol (default)
- Streamable HTTP Protocol
- Protocol selection must be configurable
- Must handle protocol-specific initialization and cleanup
- Must implement JSON-RPC 2.0 message format
- Must support stateful connections
- Must implement server and client capability negotiation
- Must support at least one of the following protocols:
-
Capabilities Declaration
- Must declare server capabilities during initialization
- Must include:
- Resources support and templates
- Tools support and list
- Prompts support and list
- Experimental features (if any)
- Must maintain capability list consistency
- Must support feature flags:
- prompts.listChanged
- resources.subscribelistChanged
- tools.listChanged
- logging
- completion
Resource Management Rules
- Resource Handling
- Must implement proper resource URI parsing
- Must support resource listing and retrieval
- Must handle resource updates and notifications
- Must validate resource access permissions
- Must follow MCP's resource primitives:
- Application-controlled contextual data
- Managed by the client application
- Examples: File contents, API responses
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.
- 8d ago First seen · 315 lines · 0 tokens per session scan A c7c1ecfe6a17
mcp-server-rules is a cursor rule published in the GitHub repository pandeussilvae/mcp-odoo-panda (8 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,821 tokens. 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
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.
cli-error-handling
CLI command error handling patterns.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.