heimdall: Instructions file for Claude Code

AGENTS.md

heimdall AGENTS.md is an instructions file for Claude Code, Codex, OpenCode from randomittin/heimdall. It costs 1,175 tokens per session, scanned A, original, MIT.

Repository instructions for Heimdall, a tool that checks other software repositories before changes are written or committed.

In plain words
What is it for?
Use them when editing Heimdall, writing its Bash tests, running its checks, or preparing commits that must pass its repository gates.
Why use it?
They prevent unfinished code from being accepted and require tests to prove that checks can detect failures.

Instructions file for Claude CodeCodexOpenCode

Written for Claude Code and Codex and OpenCode: PreToolUse hook event, but also the file is AGENTS.md. Also seen: mentions .claude-plugin; mentions CLAUDE.md; mentions Claude Code.

This is randomittin/heimdall's own configuration. It tells Claude Code, Codex and OpenCode how to work on heimdall itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything heimdall configures →

Reuse

Borrowing it

Nothing to install: this file belongs to randomittin/heimdall. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/randomittin/heimdall/main/AGENTS.md
Clone the repo
git clone --depth 1 https://github.com/randomittin/heimdall

Made for: Claude Code, Codex, OpenCode.

Wrote 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.

agentmods badge for heimdall AGENTS.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/randomittin/heimdall/agents-md/github.svg)](https://agentmods.dev/instructions/randomittin/heimdall/agents-md)
Your own site
<a href="https://agentmods.dev/instructions/randomittin/heimdall/agents-md"><img src="https://agentmods.dev/badge/instructions/randomittin/heimdall/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.

agentmods 80×15 button for heimdall AGENTS.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/randomittin/heimdall/agents-md"><img src="https://agentmods.dev/badge/instructions/randomittin/heimdall/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 1,175 This file is loaded in full into every session.
When invoked 1,175 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.01175 $0.01175
Opus 5.5 $0.00470 $0.00470
Sonnet 5.5 $0.00235 $0.00235
Haiku 4.5 $0.00118 $0.00118

Measured 7d ago against content hash 013dfbf8527b, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

heimdall 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 7d 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.

AGENTS.md · 82 lines

How it starts

The opening of the file, as written. The whole thing — 82 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Working in the Heimdall repo

Heimdall is the watchman: it gates other people's repos. So the bar here is the bar we sell. Read this before your first edit.

The rules that actually block you

  • No stub, placeholder, TODO, or skeleton code. A PreToolUse hook scans every Claude Code write for unfinished code shapes (empty bodies, not-implemented throws, # TODO comments) and refuses the write — but that hook only fires inside a live Claude Code session. bin/heimdall-gate-run's pre-commit phase backs it up at the git layer: it re-scans the staged diff against the same shared shapes (bin/lib/heimdall-stub-patterns.sh), so the ban holds no matter which tool — or human — makes the commit. If you cannot implement something fully, say so — faking it is the one failure mode this repo exists to catch.
  • Tests are bash. One file per surface: test/<name>.test.sh, run with bash test/<name>.test.sh. Exit 0 = green. A test prints PASS/FAIL lines and a count. Follow the shape of a neighbouring test rather than inventing a harness.
  • Every assertion must be falsifiable. Before you call a test done, break the thing it covers and watch it go RED, then revert and watch it go GREEN. A test that cannot fail is not a gate — it is decoration.
  • Test once, at the end. Run only the test file(s) you add or edit, once, after your changes are written; the full sweep (bash test/run-all.sh) runs once, on the final frozen tree, immediately before the landing commit — see CLAUDE.md "When the full gate runs". The break-it-and-watch-it-go-RED check above is a run on a different tree, not a repeat.
  • Batch before you sweep. Merge every pending agent result first, then run ONE sweep; never merge anything between a green sweep and its push, and never start a second sweep while one runs — see CLAUDE.md "When the full gate runs".
  • Quality gates run before push (heimdall-state check-quality-gates): tests green, lint clean, no untested changes.

Read the full file on GitHub · 82 lines

Changes

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.

  1. 7d ago Changed · +3 lines · +57 tokens per session 013dfbf8527b
  2. 10d ago Changed · +5 lines · +98 tokens per session 6cc437d47c77
  3. 1mo ago First seen · 74 lines · 1,020 tokens per session scan A e2ecdf3e1bce

Subscribe to this mod's changes

heimdall AGENTS.md is an instructions file published in the GitHub repository randomittin/heimdall (5 stars, last pushed 6d ago), licensed MIT. It adds 1,175 tokens to every session, about $0.0047 per session on Opus 5.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.

Related

Other instructions, from other repositories

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).

microsoft/vscode · 9,649 tokens

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.

vercel/next.js · 7,257 tokens

vscode oss-third-party-notices.instructions.md

Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).

microsoft/vscode · 5,262 tokens

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.

langchain-ai/langchain · 4,680 tokens

vscode copilot-instructions.md

Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).

microsoft/vscode · 2,731 tokens

deepseek-harness AGENTS.md

AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.

deepseek-ai/deepseek-harness · 4,159 tokens