Borrowing it
Nothing to install: this file belongs to arjun-krishna1/mrburns. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/arjun-krishna1/mrburns/main/AGENTS.mdgit clone --depth 1 https://github.com/arjun-krishna1/mrburnsWrote 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/arjun-krishna1/mrburns/agents-md)<a href="https://agentmods.dev/instructions/arjun-krishna1/mrburns/agents-md"><img src="https://agentmods.dev/badge/instructions/arjun-krishna1/mrburns/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.
<a href="https://agentmods.dev/instructions/arjun-krishna1/mrburns/agents-md"><img src="https://agentmods.dev/badge/instructions/arjun-krishna1/mrburns/agents-md.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.01222 | $0.01222 |
| Opus 5.5 | $0.00489 | $0.00489 |
| Sonnet 5.5 | $0.00244 | $0.00244 |
| Haiku 4.5 | $0.00122 | $0.00122 |
Grade A, and why
mrburns 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 2mo 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 — 180 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Mr. Burns Agent Instructions
Overview
Mr. Burns is a Burns/Smithers/Homer autonomous coding swarm. It coordinates multiple fresh AI agent sessions through durable JSON state files.
Role Map
- Mr. Burns - Executive oversight. Default runtime: Claude Code.
- Smithers - Planning and task decomposition. Default runtime: Claude Opus via Claude Code.
- Homers - Parallel task execution. Default runtime: Codex with GPT-5.5.
The implementation still uses generic agent types (executive, planner, worker) in state files, but user-facing docs and runtime profiles use the fable names.
Commands
# Run with the default fable role map
./burns.sh
# Force one runtime profile for every role
./burns.sh --tool claude
./burns.sh --tool codex-gpt-5.5
# Run with 8 parallel Homers
./burns.sh --workers 8
# Run Mr. Burns every 5 cycles
./burns.sh --exec-interval 5
# Full options
./burns.sh --tool fable --workers 4 --exec-interval 10 --max-cycles 100
Key Files
Orchestrator
burns.sh- Main loop that resolves runtime profiles, spawns agents, and manages cycles.
Prompts
prompts/executive.md- Mr. Burns instructions.prompts/planner.md- Smithers instructions.prompts/worker.md- Homer instructions.
State
state/project.example.json- Tracked example configuration.state/project.json- Local project goals and runtime config.state/tasks/*.json- Local task queue.state/agents/*.json- Local active agent registry.state/logs/*.log- Local per-agent activity logs.
Runtime state is ignored by git. Do not commit live state/project.json, task queues, logs, or agent registry files unless the user explicitly asks.
Libraries
lib/task.sh- Task queue operations.lib/agent.sh- Agent lifecycle helpers.lib/git.sh- Git coordination helpers.
Docs
docs/overview.md- Conceptual overview.docs/glossary.md- Terminology.docs/design/architecture.md- Technical architecture.docs/guides/configuration.md- Configuration guide.docs/reference.md- CLI, profile, schema, and signal reference.
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.
- 2mo ago First seen · 180 lines · 1,222 tokens per session scan A 9252c3730751
mrburns AGENTS.md is an instructions file published in the GitHub repository arjun-krishna1/mrburns (11 stars, last pushed 3mo ago), licensed MIT. It adds 1,222 tokens to every session, about $0.0049 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.
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).
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.
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).
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 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).
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.