Borrowing it
Nothing to install: this file belongs to gregario/hearthstone-oracle. 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/gregario/hearthstone-oracle/main/CLAUDE.mdgit clone --depth 1 https://github.com/gregario/hearthstone-oracleWrote 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/gregario/hearthstone-oracle/claude-md)<a href="https://agentmods.dev/instructions/gregario/hearthstone-oracle/claude-md"><img src="https://agentmods.dev/badge/instructions/gregario/hearthstone-oracle/claude-md.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.00654 | $0.00654 |
| Opus 5 | $0.00327 | $0.00327 |
| Sonnet 5 | $0.00131 | $0.00131 |
| Haiku 4.5 | $0.00065 | $0.00065 |
Grade A, and why
hearthstone-oracle CLAUDE.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 8d 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 — 50 lines — stays where its author put it; the contents beside it link to each section on GitHub.
hearthstone-oracle
MCP server for Hearthstone card data, strategy coaching, and deck analysis.
Stack Profiles
- MCP stack profile:
../../stacks/mcp/ - TypeScript stack profile:
../../stacks/typescript/
Read both stack profiles before writing any code.
Architecture
- Runtime data: Downloads HearthstoneJSON card data on first run, stores in
~/.hearthstone-oracle/ - Does NOT bundle card data in the npm package — data is fetched at runtime
- Updates: Checks HearthstoneJSON for newer builds, downloads only if newer
- Storage: SQLite via
better-sqlite3with FTS5 full-text search - Two layers: Layer 1 (card data from HearthstoneJSON) + Layer 2 (curated strategy knowledge)
Data Source
HearthstoneJSON (hearthstonejson.com) — HearthSim community project. Unrestricted use. Auto-extracted from game files.
Engineering
Uses Superpowers for engineering execution. Follow TDD workflow: write tests first, then implement.
Important
- All logging via
console.error()— neverconsole.log()(corrupts stdio JSON-RPC) - In-memory database for tests:
getDatabase(':memory:') - Run
/mcp-qabefore every commit — no exceptions
HearthstoneJSON dbfId drift
What it is. dbfIds (the integer IDs encoded inside Hearthstone deckstrings) are NOT stable across HearthstoneJSON snapshots. The same logical card can be assigned a new dbfId between data drops, and old dbfIds can be reused for unrelated cards. Examples observed during the deck-decode fix session:
- Reno Jackson (
LOE_011):27228→2883(with a Core reprint at76314). - Tirion Fordring (
EX1_383):391→890. The legacy391now resolves to Perdition's Blade, a completely different card. - Stonetusk Boar (
CS2_171):604→648.
Why it happens. This is a property of how HearthstoneJSON extracts and re-emits the card database from game files — not a bug in our pipeline. We consume the snapshot as-is.
What we do about it.
- Snapshot TTL: the data pipeline refreshes from HearthstoneJSON on a TTL so we converge on the latest dbfIds.
- Fallback message:
decode_deckreturns a clear placeholder for any dbfId not present in the local snapshot ("possibly added in a recent expansion; refresh data to resolve"), with the dbfId surfaced for lookup. - Test fixtures: seed data uses dbfIds from a recent snapshot. When fixtures drift, refresh them rather than freezing on legacy IDs.
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.
- 8d ago First seen · 50 lines · 654 tokens per session scan A 53579b609f35
hearthstone-oracle CLAUDE.md is an instructions file published in the GitHub repository gregario/hearthstone-oracle (1 stars, last pushed 4mo ago), licensed MIT. It adds 654 tokens to every session, about $0.0033 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).
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.
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.