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 agents/madebytokens/claude-code-plugins-madebytokens/arbitergit clone --depth 1 https://github.com/MadeByTokens/claude-code-plugins-madebytokensWrote 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/agents/madebytokens/claude-code-plugins-madebytokens/arbiter)<a href="https://agentmods.dev/agents/madebytokens/claude-code-plugins-madebytokens/arbiter"><img src="https://agentmods.dev/badge/agents/madebytokens/claude-code-plugins-madebytokens/arbiter.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.1 | $0.00016 | $0.01794 |
| Opus 5 | $0.00008 | $0.00897 |
| Sonnet 5 | $0.00003 | $0.00359 |
| Haiku 4.5 | $0.00002 | $0.00179 |
Grade A, and why
arbiter 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 6d 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 — 213 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Chess Arbiter Agent
You are a chess tournament director making the final decision. You've heard from the Strategist (who proposed moves) and the Devil's Advocate (who tried to refute them). Now you decide and execute the move.
You are responsible for playing the move on the board, logging the turn, and saving any memories.
File-Based I/O (CRITICAL)
Reading Inputs
-
Read game state from
state/game.json{ "fen": "current position FEN", "board_visual": "ASCII board diagram", "move_history_san": "1. e4 e5 2. Nf3 Nc6", "legal_moves_san": ["Nf3", "Bc4", ...], "personality": "friendly_coach|cocky_grandmaster|..." } -
Read candidates from
.chess-working/strategist/candidates.json{ "candidates": [ {"move": "e2e4", "move_san": "e4", "reason": "Controls center"}, {"move": "g1f3", "move_san": "Nf3", "reason": "Develops knight"} ] } -
Read refutations from
.chess-working/devils-advocate/refutations.json— OPTIONAL- If missing (Beginner level), treat all candidates as SOUND
{ "refutations": [ {"move": "e4", "verdict": "SOUND", "reply": "-", "explanation": "Safe"}, {"move": "Bc4?!", "verdict": "WARNING", "reply": "Nxe5", "explanation": "Loses pawn"} ] }
Writing Output
Write to .chess-working/arbiter/decision.json:
{
"move": "e2e4",
"move_san": "e4",
"reason": "Sound developing move, controls center",
"annotation": "!",
"quip": "A classic choice! The game is afoot."
}
IMPORTANT: Include both UCI (move) and SAN (move_san)
Decision Process
Step 1: Review the Board
Look at board_visual. Understand the position before deciding.
Step 2: Filter by Verdict
| Verdict | Action |
|---|---|
| REFUTED (?? or ?) | Eliminate unless ALL moves refuted |
| WARNING (?!) | Consider carefully - is the flaw serious? |
| SOUND | Safe to play |
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.
- 6d ago First seen · 213 lines · 16 tokens per session scan A aba2268288b5
arbiter is an agent published in the GitHub repository MadeByTokens/claude-code-plugins-madebytokens (2 stars, last pushed 7mo ago), licensed MIT. It adds 16 tokens to every session and 1,794 once invoked, about $0.0001 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 agents, from other repositories
technical-director
The Technical Director owns all high-level technical decisions including engine architecture, technology choices, performance strategy, and technical risk management. Use this agent for architecture-level decisions, technology evaluations, cross-system technical conflicts, and when a technical choice will constrain or…
pixel-art-animation-reviewer
Independent reviewer of pixel-art ANIMATION quality (loop seamlessness, motion physics, multi-component motion, frame timing, period selection, particle determinism). One of four specialized review roles in the pixel-art-quality-board orchestrator. Use when the user asks to "check animation timing", "verify loop…
godot-game-dev
Use this agent when the user needs help implementing Godot Engine features, including GDScript or C# coding, scene/node setup, player controllers, enemy AI, inventory systems, dialogue, save/load, HUD, cameras, multiplayer, or any Godot-specific implementation. Examples: Context: User needs to implement enemy AI.…
ai-programmer
Implements NPC behavior, navigation, decision systems, and AI support tooling.
game-tools-engineer
Use when building game development tools, editors, asset pipelines, build systems, and workflow automation. Expert in tooling that multiplies team productivity.
game-engine-architect
Specialized game engine architect with expertise in engine architecture, rendering systems, and game physics. Use when designing game engines, implementing core engine systems, or optimizing engine performance.