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/mrg4dget/5e-tools-mcp/cursorrulesgit clone --depth 1 https://github.com/MrG4dget/5e-tools-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.00485 | $0.00485 |
| Opus 5 | $0.00243 | $0.00243 |
| Sonnet 5 | $0.00097 | $0.00097 |
| Haiku 4.5 | $0.00049 | $0.00049 |
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 2d 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.
This is a copy
88% identical to mcp-5etools-core — 23 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
Cursor Rules — mcp-5etools
Purpose
Cursor, treat this repository as an MCP server exposing 5eTools data to LLMs. The 5etools-src/ folder at project root is read-only input. Do not rewrite or reformat upstream data files.
High-level goals
- Implement stable MCP tools/resources for search, fetch, and render of 5eTools entities.
- Prefer 2024 rules when an entity exists in both 2014 and 2024, unless explicitly requested otherwise.
- Ensure all generated text links back to
fiveet://entity/{kind}/{source}/{slug}URIs. - Keep rendering deterministic, resolving common
{@...}tags.
Architecture boundaries
src/server.tsis the entry point; all file I/O and indexing stays undersrc/.- The data path defaults to
./5etools-src. Allow override withFIVETOOLS_SRC_DIRenv var. - Avoid global state leakage; keep indices in a simple in-memory cache for now.
Tasks to prefer
- Add more
{@tag}handlers in the renderer with unit tests. - Add fuzzy search and ranking (e.g., minisearch) with facets.
- Add
list_sources,get_rules_section,resolve_tagtools. - Write schema/resource docs (
ARCHITECTURE.md) when types grow.
Tasks to avoid
- Editing anything inside
5etools-src/. - Introducing non-deterministic rendering (e.g., random ordering, timestamps).
- Over-fetching: return
resource_linkwhen possible.
Coding standards
- TypeScript strict mode; no
anyin public types. - Small, composable functions; prefer pure utilities for rendering.
- Keep dependencies minimal (MCP SDK, zod).
PR/commit hygiene
- One logical concern per PR.
- Update README/ARCHITECTURE when changing surfaces.
- Include quick tests for any new tag handler.
Prompts for in-IDE use
- “When unsure, call a tool. Don’t hallucinate rules text.”
- “Prefer 2024 rules unless told otherwise.”
- “Always include source abbreviations in results.”
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.
- 2d ago First seen · 42 lines · 485 tokens per session scan A 91a0c3c6eeec
cursorrules is a cursor rule published in the GitHub repository MrG4dget/5e-tools-mcp (2 stars, last pushed 1y ago), licensed MIT. It adds 485 tokens to every session, about $0.0024 per session on Opus 5. A static security scan graded it A with 0 findings. It is 88% identical to mcp-5etools-core, differing in 23 lines, and is treated as a copy.
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.