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/MrG4dget/5e-tools-mcpWrote 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/mrg4dget/5e-tools-mcp/10-mcp-tools)<a href="https://agentmods.dev/rules/mrg4dget/5e-tools-mcp/10-mcp-tools"><img src="https://agentmods.dev/badge/rules/mrg4dget/5e-tools-mcp/10-mcp-tools.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.00018 | $0.00366 |
| Opus 5 | $0.00009 | $0.00183 |
| Sonnet 5 | $0.00004 | $0.00073 |
| Haiku 4.5 | $0.00002 | $0.00037 |
Grade A, and why
10-mcp-tools 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 6d 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.
What it actually says
Tool Selection Guide
Use these tools instead of guessing:
-
search_entities({ query, kinds?, sources?, ruleset?, limit? })- Use for name-based lookup or comparisons. The server fuzzy-ranks results.
- Include
kindsandruleset: "2024"when you need the 2024 version.
-
get_entity({ uri? | key, format? })- Fetch the canonical record. Prefer
format: "markdown"for chat-ready text.
- Fetch the canonical record. Prefer
-
render_entries({ entries })- Convert 5eTools
entriesand inline{@tags}to Markdown/HTML.
- Convert 5eTools
-
list_sources({ ruleset?, kind? })- Discover available sources (e.g., xPHB/xDMG/xMM).
-
get_rules_section({ slugOrTitle, ruleset? })- Pull glossary/rules text by title/slug. Prefer 2024 unless told otherwise.
-
resolve_tag({ tag })- Normalize inline tags (e.g.,
{@spell fireball|PHB}) to canonical URIs.
- Normalize inline tags (e.g.,
Return Shape Expectations
search_entitiesreturnsresource_linkitems. Use the URI(s) withget_entityas needed.get_entitywithformat:"json"returns structured data; with"markdown"returns rendered text.
Patterns
- Comparisons: call
search_entitiesthenget_entityfor each candidate and produce a table. - Disambiguation: if multiple sources match, prefer 2024 by default.
@README.md
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.
- 6d ago First seen · 38 lines · 18 tokens per session scan A 14e307dc6079
10-mcp-tools is a cursor rule published in the GitHub repository MrG4dget/5e-tools-mcp (2 stars, last pushed 1y ago), licensed MIT. It adds 18 tokens to every session and 366 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
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-assertions-over-defensive-checks
Prefer assertions over defensive checks when data is guaranteed to be valid.
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.