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/evtapps/ditto-mcp/mcp-servergit clone --depth 1 https://github.com/evtapps/ditto-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.00015 | $0.00351 |
| Opus 5 | $0.00008 | $0.00176 |
| Sonnet 5 | $0.00003 | $0.00070 |
| Haiku 4.5 | $0.00002 | $0.00035 |
Grade A, and why
mcp-server 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
MCP Server Practices
Tools
- Register tools in
createServer()only; keep handlers small and deterministic. inputSchema: define with Zod field shapes (e.g.,{ param: z.string() }) or az.object({ ... })shape assigned to a constant and passed as fields. Keep numeric constraints (int,positive, upper bounds) andurl()where applicable.- Validate user input strictly (minLength, numeric constraints, URL where applicable).
- Return
{ content: [...] }on success;{ isError: true, content: [...] }on failure. Keep error content concise and actionable. - Error content should be concise, actionable, and safe (no secrets).
Resources
- Use readable titles and descriptions. Keep resource bodies small and redacted if they include configuration. Only expose non-sensitive fields in resources like
ditto://config.
Guardrails
- Always enforce single-statement DQL and detect the first token (
SELECT|INSERT|UPDATE|DELETE|EVICT). Strip comments before tokenizing. - Enforce operation allow-list from config. Default to
SELECTonly. - If configured, require the DQL to match at least one allow-list regex.
Configuration Access
- Tool handlers do not read env directly. Resolve base URL, API key, and timeouts from the
ServerConfigbuilt inloadConfig().
Errors
- Prefer returning an error content block over throwing; throwing should be reserved for truly unexpected conditions.
- The Ditto client should convert failures into a Ditto-like envelope to keep tool handlers simple.
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 · 31 lines · 15 tokens per session scan A 7387811028d1
mcp-server is a cursor rule published in the GitHub repository evtapps/ditto-mcp (0 stars, last pushed 9mo ago), licensed MIT. It adds 15 tokens to every session and 351 once invoked, about $0.0001 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.
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.
family-instance-domain-actions
Family instance domain action implementation patterns.