Irrlicht: Instructions file for Codex

AGENTS.md

Irrlicht AGENTS.md is an instructions file for Codex, OpenCode from ingo-eichhorst/Irrlicht. It costs 4,149 tokens per session, scanned A, original, MIT.

A set of development instructions for the Irrlicht project, including shortcuts, process rules, build guidance, and required evidence for dismissing issues.

In plain words
What is it for?
Use it when working on Irrlicht, especially for issue execution, build artifacts, daemon work, and decisions that need supporting evidence.
Why use it?
It provides project-specific rules so development work follows the repository’s process and does not use prohibited workflows.

Instructions file for CodexOpenCode

Written for Codex and OpenCode: the file is AGENTS.md. Also seen: reads .claude/ paths; mentions CLAUDE.md; mentions subagents.

This is ingo-eichhorst/Irrlicht's own configuration. It tells Codex and OpenCode how to work on Irrlicht 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 Irrlicht configures →

Reuse

Borrowing it

Nothing to install: this file belongs to ingo-eichhorst/Irrlicht. 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/ingo-eichhorst/Irrlicht/main/AGENTS.md
Clone the repo
git clone --depth 1 https://github.com/ingo-eichhorst/Irrlicht

Made for: 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 Irrlicht AGENTS.md

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

Your own site · 80×15
<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="Reviewed on agentmods" width="80" height="20"></a>
Per session 4,149 This file is loaded in full into every session.
When invoked 4,149 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.04149 $0.04149
Opus 5.5 $0.01660 $0.01660
Sonnet 5.5 $0.00830 $0.00830
Haiku 4.5 $0.00415 $0.00415

Measured 1mo ago against content hash 8173d0aa2315, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 1mo 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 · 260 lines

How it starts

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

Irrlicht — Development Guide

Short Cuts

  • Triage and plan an issue with /ir:triage #<N>. Execute the approved plan with /ir:exec <N>. The execution skill produces a ready PR and never merges.
  • Run several tickets at once with /ir:fleet <N> <N> — it groups by declared file scope, verifies each hand-back with a checker rather than a reading, and merges nothing. See ci-gates.md for the wait and gate-scoping rules a concurrent run depends on.
  • 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.sh reads the base version from version.json and produces signed universal binaries + the installer. The binary's --version output is the bare version (e.g. 0.3.13) so release tags stay clean.
  • Dev builds: tools/build-dev.sh produces a native binary at core/bin/irrlichd with a version string like 0.3.13+1f702e7.dirty — base version plus short SHA plus .dirty if 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 --base for the bare version.json value). promote-recording.sh captures it into archive and top-level manifest.json files so the viewer's metadata panel shows which dev build produced each recording.

Read the full file on GitHub · 260 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. 1mo ago Changed · +6 tokens per session 8173d0aa2315
  2. 1mo ago Changed · +4 lines · +75 tokens per session 017f34dfb57b
  3. 1mo ago Changed 2404c3f28c32
  4. 1mo ago Changed · +8 lines · +150 tokens per session ec3a43f6b6b6
  5. 1mo ago Changed · -3 lines · -30 tokens per session 449789ed8fc3
  6. 1mo ago Changed · +7 lines · +117 tokens per session c22d898848aa
  7. 1mo ago First seen · 244 lines · 3,831 tokens per session scan A f172d6c7d698

Subscribe to this mod's changes

Irrlicht AGENTS.md is an instructions file published in the GitHub repository ingo-eichhorst/Irrlicht (101 stars, last pushed today), licensed MIT. It adds 4,149 tokens to every session, about $0.0166 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-30.

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,715 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,581 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

deno copilot-instructions.md

Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.

denoland/deno · 3,077 tokens