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/hashintel/hash/agents-mdgit clone --depth 1 https://github.com/hashintel/hashWhat 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.02119 | $0.02119 |
| Opus 5 | $0.01059 | $0.01059 |
| Sonnet 5 | $0.00424 | $0.00424 |
| Haiku 4.5 | $0.00212 | $0.00212 |
Grade A, and why
hash 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 yesterday.
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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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.
- yesterday First seen · 146 lines · 2,119 tokens per session scan A 0546b77fe795
hash AGENTS.md is an instructions file published in the GitHub repository hashintel/hash (1,649 stars, last pushed yesterday), with no licence file. It adds 2,119 tokens to every session, about $0.0106 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-30.
Other instructions, from other repositories
deno copilot-instructions.md
Instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.
deno CLAUDE.md
Instructions for denoland/deno, covering deno development guide, git workflow, high level overview, key directories and quick start.
better-result AGENTS.md
Instructions for dmmulroy/better-result, covering better-result, structure, where to look, code map and conventions.
Better-Fullstack AGENTS.md
Instructions for Marve10s/Better-Fullstack, covering guidelines, web ui, workflow and bun.
pisper AGENTS.md
Instructions for ling-kong-ran/pisper, covering agents.md, project, architecture, commands and setup.
Better-Fullstack CLAUDE.md
Instructions for Marve10s/Better-Fullstack, covering claude.md, code style, general preferences and picking the right models for workflows and subagents.