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/dravensoft-dev/arena/claude-mdgit clone --depth 1 https://github.com/dravensoft-dev/arenaWhat 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.00177 | $0.00177 |
| Opus 5 | $0.00088 | $0.00088 |
| Sonnet 5 | $0.00035 | $0.00035 |
| Haiku 4.5 | $0.00018 | $0.00018 |
Grade A, and why
arena CLAUDE.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 2d 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.
What it actually says
CLAUDE.md
Two branches, and this file is neither. Pick one before you read anything else.
- Building something with Arena, a screen, a prototype, a skin, an integration:
skills/design/SKILL.md. - Changing Arena itself, a component, a token, a contract, a gate, a release:
AGENTS.md.
This file carries no rule of its own. It exists because a harness that loads CLAUDE.md and
nothing else would otherwise land on whichever branch this file happened to name, and landing on
the wrong one is how a short question turns into a long read. Two routers that can disagree are
worse than one, so both of the above are stated once, on the other side of their own link.
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.
- 2d ago First seen · 12 lines · 177 tokens per session scan A 0f57cbd16ed2
arena CLAUDE.md is an instructions file published in the GitHub repository dravensoft-dev/arena (2 stars, last pushed 10d ago), licensed MIT. It adds 177 tokens to every session, about $0.0009 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-31.
Other instructions, from other repositories
spartan CLAUDE.md
Instructions for spartan-ng/spartan, covering working in this repo (notes for claude / ai agents), before pushing: run the ci checks locally and pull requests.
kolibri copilot-instructions.md
Copilot instructions for public-ui/kolibri, covering github copilot instructions for kolibri repository, kolibri overview, essential setup commands, 1. install node.js 22 and 2. enable pnpm.
kolibri AGENTS.md
AGENTS.md instructions for public-ui/kolibri, covering agent instructions, handling hints, 🚨 format-first rule, semantic versioning and project structure.
ng-blatui AGENTS.md
Instructions for anousss007/ng-blatui, covering ng-blatui — agent guide, use the official angular tooling, hard rules (this repo), commands and after changing a component's public api.
core-web copilot-instructions.md
Copilot instructions for db-ux-design-system/core-web: All development instructions, build commands, validation steps, coding rules, and the pull request workflow are maintained in AGENTS.md at the repository root. Read that file first before starting any task.
core-web AGENTS.md
AGENTS.md instructions for db-ux-design-system/core-web, covering db ux design system v3 core web, working effectively, required prerequisites, bootstrap and setup and build and test.