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.
npx agentmods add instructions/dfieser/hea-bench/agents-mdgit clone --depth 1 https://github.com/dfieser/hea-benchWhat 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 | $0.06825 | $0.06825 |
| Opus 5 | $0.03413 | $0.03413 |
| Sonnet 5 | $0.01365 | $0.01365 |
| Haiku 4.5 | $0.00683 | $0.00683 |
Grade A, and why
hea-bench 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 2d 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 — 517 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
Machine-oriented usage guide for hea-bench. If you are an AI coding
agent integrating this library into another project, read this first.
It tells you the public API, exact return types and units, the
fastest path to each common task, and the mistakes to avoid. Every
snippet here is copy-pasteable and was checked against the shipped
code.
Editing this repo's own docs (or this file)? Follow the writing rule in CONTRIBUTING.md: minimize jargon and explain any necessary term inline in plain language, and always state what a number is and its units. Don't defer to a glossary.
What this is
hea-bench is an open, interpretable calculator of the standard
high-entropy-alloy (HEA) thermodynamic and geometric descriptors plus
the canonical empirical phase-prediction rules. Every quantity is a
transparent closed-form expression over a curated element-property
table — no fitted model, no black box.
One calculation core, three surfaces:
- Python library + CLI — this package (
pip install hea-bench). - Zero-install browser app —
web/index.html(hosted at https://dfieser.github.io/hea-bench/; the page is the calculator). - Native desktop app — a single offline executable that wraps the browser app via Tauri.
- MCP server —
pip install "hea-bench[mcp]"then runhea-bench-mcp(stdio). Thirteen deterministic tools over this same library:parse_composition, batchalloy_descriptors/alloy_rules,omega_sensitivity(pair-table robustness check),oxide_report,element_coverage,corpus_query/corpus_describe(the provenance-tracked corpus; needs the locally built data),predict_properties(intervals and domain flags at payload top level),check_applicability,design_search(hard caps enforced),campaign_suggest(operates on a user-supplied campaign file), andabout, which reports per-capability availability. Every response carries units or uncertainty fields, a citation key where a parametrization is involved, and the library version. If you are an agent with MCP support, prefer those tools over reimplementing the formulas below; if not, the Python API is identical.
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.
- 2d ago First seen · 517 lines · 6,825 tokens per session scan A 47c446598d9e
hea-bench AGENTS.md is an instructions file published in the GitHub repository dfieser/hea-bench (1 stars, last pushed 8d ago), licensed MIT. It adds 6,825 tokens to every session, about $0.0341 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
calculator-mcp-server AGENTS.md
AGENTS.md instructions for cyanheads/calculator-mcp-server, covering agent protocol, mcp surface, security model, what's next? and core rules.
calculator-mcp-server CLAUDE.md
Claude Code instructions for cyanheads/calculator-mcp-server, covering agent protocol, mcp surface, security model, what's next? and core rules.
jacobian AGENTS.md
Instructions for morluto/jacobian, covering jacobian agent guide, what we are building, non-negotiable boundaries, implement mathematics directly and mathematical boundedness is a proof obligation.
OpenQuantum AGENTS.md
Instructions for xi-zhao/OpenQuantum, covering openquantum, 四个职责面, 扩展对象不可混用, 不变量 and 代码位置.
calc-mcp CLAUDE.md
Instructions for coo-quack/calc-mcp, covering project rules, tech stack, commands, project structure and tool architecture.
cdc-health-mcp-server CLAUDE.md
Instructions for cyanheads/cdc-health-mcp-server, covering agent protocol, domain, api surface, socrata api endpoints and cdc wonder api.