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-validate)<a href="https://agentmods.dev/commands/crabsmadethis/d2r-horadric-tools/d2r-validate"><img src="https://agentmods.dev/badge/commands/crabsmadethis/d2r-horadric-tools/d2r-validate/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-validate"><img src="https://agentmods.dev/badge/commands/crabsmadethis/d2r-horadric-tools/d2r-validate.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.00012 | $0.00213 |
| Opus 5 | $0.00006 | $0.00106 |
| Sonnet 5 | $0.00002 | $0.00043 |
| Haiku 4.5 | $0.00001 | $0.00021 |
Grade A, and why
d2r-validate 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 10d 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 Validate
Validate the YAML definition for $ARGUMENTS without building or deploying.
python3 -m d2r_chargen validate $ARGUMENTS
This checks:
- YAML syntax and schema
- Item UIDs exist in data files (Rule 1)
- Item codes match base types in item_bases.py
- Stat aliases resolve via PROPERTY_ALIASES (Rule 14)
- Runeword indices exist in runewords.py
- Socket filler validity
No .d2s files are written or modified. Safe to run at any time.
Follow-up
If validation passes and you want to build:
- Use
/d2r-build $ARGUMENTSfor the full safe build cycle
If validation fails:
- Fix the YAML in
chars/$ARGUMENTS.yaml - Re-run validation before attempting a build
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.
- 10d ago First seen · 32 lines · 12 tokens per session scan A e13442a31cfe
d2r-validate is a command published in the GitHub repository crabsmadethis/d2r-horadric-tools (4 stars, last pushed 1mo ago), licensed MIT. It adds 12 tokens to every session and 213 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
ui-aqa-flow-code-analysis
Phase 3 Code Analysis of ui-aqa-flow.
ui-aqa-flow-test-report-analysis
Phase 7 Test Report Analysis of ui-aqa-flow.
api-aqa-flow-execution-and-report-analysis
Phase 6 Execution & Report Analysis of api-aqa-flow (USER INTERACTION REQUIRED).
audio-pass
Functional audio review for implementation, mix coverage, clarity, and player feedback.
regression-suite
Map test coverage to GDD critical paths.
godot-runtime-verify
Verify a built Godot 2D or 3D scene at runtime: run the scene (press-play or headless), read the captured debugger output, classify any runtime errors against a Godot-specific taxonomy, and decide a PASS/FAIL runtime gate for the slice's acceptance behavior. The run's real output IS the Layer-1 runtime evidence…