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/crabsmadethis/d2r-horadric-toolsWrote 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/commands/crabsmadethis/d2r-horadric-tools/d2r-lookup)<a href="https://agentmods.dev/commands/crabsmadethis/d2r-horadric-tools/d2r-lookup"><img src="https://agentmods.dev/badge/commands/crabsmadethis/d2r-horadric-tools/d2r-lookup/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/crabsmadethis/d2r-horadric-tools/d2r-lookup"><img src="https://agentmods.dev/badge/commands/crabsmadethis/d2r-horadric-tools/d2r-lookup.svg" alt="Reviewed on agentmods" width="80" 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.00021 | $0.00476 |
| Opus 5 | $0.00010 | $0.00238 |
| Sonnet 5 | $0.00004 | $0.00095 |
| Haiku 4.5 | $0.00002 | $0.00048 |
Grade A, and why
d2r-lookup 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 11d 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
D2R Data Lookup
Look up $ARGUMENTS in the D2R game data files.
How to Look Up
Use the MCP data tools (d2r-data server). These query the extracted game data in d2r_chargen/data/ — the ONLY authoritative source (Rule 9).
By type (when you know what you're looking for):
d2r_lookup_unique— unique items by name/UIDd2r_lookup_set_item— set items by name/IDd2r_lookup_item_base— base items by 3-char code or named2r_lookup_runeword— runewords by name/ID (includes runes, valid bases, stats)d2r_lookup_stat— stats by ID, canonical name, or alias (includes encoding params)d2r_lookup_skill— skills by name/ID
Cross-type search (when you're not sure):
d2r_search— searches uniques, sets, runewords, and bases
Rules
- Rule 1: NEVER hallucinate UIDs, item codes, or binary format values. Every value MUST come from the data files.
- Rule 9: NEVER trust web research for D2R game data. If data isn't in these files, it doesn't exist.
- Rule 14: Verify stat aliases against
d2r_chargen/config.pyPROPERTY_ALIASES.
Data File Locations
All in d2r_chargen/data/:
unique_items.py+unique_item_stats.py— unique item definitions and statsset_items.py— set item definitionsitem_bases.py— base item types (dimensions, requirements, sockets)runewords.py+runeword_stats.py— runeword definitions and statsitem_stat_cost.py— stat encoding parameters (save_bits, save_add, etc.)skills.py— skill definitions
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.
- 11d ago First seen · 40 lines · 21 tokens per session scan A e7f3ccbbb23a
d2r-lookup is a command published in the GitHub repository crabsmadethis/d2r-horadric-tools (4 stars, last pushed 1mo ago), licensed MIT. It adds 21 tokens to every session and 476 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 commands, from other repositories
add-tool
Build a new UEFN Toolbelt tool named "$ARGUMENTS". Follow the tool-developer agent workflow exactly.
publish-check
Run a full pre-publish audit. Check everything before the user submits their island to Fortnite.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.