Borrowing it
Nothing to install: this file belongs to crabsmadethis/d2r-horadric-tools. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/crabsmadethis/d2r-horadric-tools/main/AGENTS.mdgit 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/instructions/crabsmadethis/d2r-horadric-tools/agents-md)<a href="https://agentmods.dev/instructions/crabsmadethis/d2r-horadric-tools/agents-md"><img src="https://agentmods.dev/badge/instructions/crabsmadethis/d2r-horadric-tools/agents-md/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/instructions/crabsmadethis/d2r-horadric-tools/agents-md"><img src="https://agentmods.dev/badge/instructions/crabsmadethis/d2r-horadric-tools/agents-md.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.00832 | $0.00832 |
| Opus 5 | $0.00416 | $0.00416 |
| Sonnet 5 | $0.00166 | $0.00166 |
| Haiku 4.5 | $0.00083 | $0.00083 |
Grade A, and why
d2r-horadric-tools AGENTS.md 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.
How it starts
The opening of the file, as written. The whole thing — 108 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Instructions
This is a public Diablo II: Resurrected tooling repository. Keep every change usable by a GitHub reader who has only this repo and their own local D2R install.
Read First
Before editing, read the files relevant to the task:
README.mdCONTRIBUTING.mdCLAUDE.mddocs/d2s_format.mdfor save-format workd2r_mcp/README.mdfor MCP tool changes
Public Boundary
Committed content must be public-safe. Do not add:
- personal
.d2ssaves or raw save corpora - raw memory dumps or live process captures
- machine-local paths, account identifiers, tokens, or secrets
- extracted Blizzard game data
- internal planning notes, disposable probe queues, or live-session diaries
- recovered private source or references that require private repositories to understand this project
Public docs may include source behavior, CLI and MCP usage, synthetic fixtures, sanitized binary-layout findings, repeatable validation commands, known limitations, and open research questions that belong to this public toolkit.
If local manual validation matters, record the stable technical result and a repeatable public procedure. Leave private artifacts and machine-specific details out of the repo.
Save-File Rules
For .d2s work:
- Prefer targeted edits over rebuilding a save from scratch.
- Back up before writing any local save file.
- Write to temp or staging files first.
- Run the scanner after every edit phase.
- Verify checksums and file-size fields.
- Promote only after validation passes.
- Do not stack risky edits before scanning.
- Treat scanner hard errors as deployment blockers unless bit-level evidence proves the scanner is wrong.
Use repo-generated data modules for D2R constants. Do not use web research as the source of truth for item UIDs, item codes, stat encoding, runeword indices, or skill IDs.
MCP Rules
MCP tool changes require synchronized docs and tests. If you add, remove,
rename, or change a tool in d2r_mcp/, update:
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 · 108 lines · 832 tokens per session scan A a320c2443989
d2r-horadric-tools AGENTS.md is an instructions file published in the GitHub repository crabsmadethis/d2r-horadric-tools (4 stars, last pushed 1mo ago), licensed MIT. It adds 832 tokens to every session, about $0.0042 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 instructions, from other repositories
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.