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/ingo-eichhorst/irrlicht/agents-mdgit clone --depth 1 https://github.com/ingo-eichhorst/IrrlichtWrote 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/ingo-eichhorst/irrlicht/agents-md)<a href="https://agentmods.dev/instructions/ingo-eichhorst/irrlicht/agents-md"><img src="https://agentmods.dev/badge/instructions/ingo-eichhorst/irrlicht/agents-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 | $0.03948 | $0.03948 |
| Opus 5 | $0.01974 | $0.01974 |
| Sonnet 5 | $0.00790 | $0.00790 |
| Haiku 4.5 | $0.00395 | $0.00395 |
Grade A, and why
Irrlicht 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 today.
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 — 251 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Irrlicht — Development Guide
Short Cuts
- Issue execution is handled entirely by the
ir:execskill:/ir:exec [mode] <N>(mode defaults toauto) — see its "Modes" section (.claude/skills/ir:exec/SKILL.md) for what each mode does. - NEVER RUN: the Workflow tool (multi-agent orchestration) if not explicitly requested (too expensive)
Process Rules
Worktrees share the parent repo's .git dir, so git stash is not isolated per worktree — it's a single shared stack. Concurrent agents stashing in different worktrees can pop each other's WIP. Use a local commit as a checkpoint instead (git commit -m wip, amend/reset later).
When encountering suboptimal processes or issues make improvment suggestions in you final answer to the user.
Dismissals carry evidence. Any claim whose function is "you don't need to look here" — already fixed in #X, self-heals, likely benign, non-issue — gets the same bar as the claim it supports: cite what you ran or read, or mark it assumed. This binds wherever a finding is written down (issue bodies, PR descriptions, triage comments, final answers), because a wrong dismissal is the one kind of error that stops anyone from checking it. Marking works: in #1088 every claim explicitly labelled "unverified" was investigated and came back not real, while that issue's one real bug hid in an unmarked aside.
Build Artifacts
Use ./.build for build artifacts.
Building the daemon
- Release builds:
tools/build-release.shreads the base version fromversion.jsonand produces signed universal binaries + the installer. The binary's--versionoutput is the bare version (e.g.0.3.13) so release tags stay clean. - Dev builds:
tools/build-dev.shproduces a native binary atcore/bin/irrlichdwith a version string like0.3.13+1f702e7.dirty— base version plus short SHA plus.dirtyif the worktree has uncommitted changes.+is semver build metadata so dev binaries never compare as "newer" than their base release. - The string is computed by
tools/version.sh(pass--basefor the bare version.json value).promote-recording.shcaptures it into archive and top-levelmanifest.jsonfiles so the viewer's metadata panel shows which dev build produced each recording.
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.
- today Changed · +7 lines · +117 tokens per session c22d898848aa
- 4d ago First seen · 244 lines · 3,831 tokens per session scan A f172d6c7d698
Irrlicht AGENTS.md is an instructions file published in the GitHub repository ingo-eichhorst/Irrlicht (96 stars, last pushed today), licensed MIT. It adds 3,948 tokens to every session, about $0.0197 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
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.
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.
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.
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).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.