What is batty CLAUDE.md?

Repository instructions for Batty, a Rust command-line system that runs a coordinated team of coding agents inside terminal windows. They describe its architecture, tools, configuration files, and development principles.

They help agents set up and modify Batty, understand its Rust source and runtime components, work with YAML configuration and Markdown tasks, and follow its development guidance.

They give agents the project context needed to change Batty without guessing how its agents, terminal sessions, task board, and logs fit together. They also identify the required technologies and file formats.

How battysh/batty configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to battysh/batty. 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/battysh/batty/main/CLAUDE.md

Clone the repo

git clone --depth 1 https://github.com/battysh/batty

Made for: Claude Code.

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.

README.md

[![agentmods](https://agentmods.dev/badge/instructions/battysh/batty/claude-md/github.svg)](https://agentmods.dev/instructions/battysh/batty/claude-md)

Your own site

<a href="https://agentmods.dev/instructions/battysh/batty/claude-md"><img src="https://agentmods.dev/badge/instructions/battysh/batty/claude-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.

Your own site · 80×15

<a href="https://agentmods.dev/instructions/battysh/batty/claude-md"><img src="https://agentmods.dev/badge/instructions/battysh/batty/claude-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 1,511 This file is loaded in full into every session.

When invoked 1,511 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.

Model	Per session	Once invoked
Fable 5.1	$0.01511	$0.01511
Opus 5.5	$0.00604	$0.00604
Sonnet 5.5	$0.00302	$0.00302
Haiku 4.5	$0.00151	$0.00151

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

Security

Grade A, and why

batty 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 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.

CLAUDE.md · 137 lines

How it starts

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

Batty — Agent Instructions

What Is This Project

Batty is a hierarchical agent command system for software development. It runs a small team of agents inside tmux, routes messages between roles, tracks work on a shared Markdown board, and keeps the whole run visible in the terminal.

See planning/architecture.md for the system design and planning/dev-philosophy.md for development principles.

Tech Stack

Language: Rust
CLI framework: clap
Terminal runtime: tmux (pane layout, display-only surfaces when shim mode is active, session persistence)
Agent shim: PTY-owning subprocess per agent, screen classification, structured socketpair protocol (src/shim/)
PTY support: portable-pty (used by shim runtime for agent PTY management)
Async runtime: tokio
Config format: YAML (.batty/team_config/team.yaml)
Board format: Markdown tasks with YAML frontmatter
Execution logs: JSON lines

Project Structure

src/               # Rust source
  shim/            # Agent shim runtime (PTY, state classifier, protocol, chat)
docs/              # User and reference documentation
assets/            # Static assets (images, demos)
scripts/           # Utility scripts
planning/          # Architecture, roadmap, philosophy docs
.agents/           # Codex agent rules/skills
.claude/           # Claude agent rules/skills
.batty/
  team_config/
    team.yaml      # Team topology, routing, layout, timing
    *.md           # Role prompts used to launch architect/manager/engineer agents
    board/         # Shared task board and task files
    events.jsonl   # Team event log

Development Principles

Compose, don't monolith. Use existing CLI tools where possible.
Markdown as backend. Keep state human-readable and git-versioned.
Minimal code. Build the smallest thing that works.
No premature abstraction. Prefer obvious code over clever indirection.
Test what matters. Focus on tmux supervision, message routing, board state, and prompt handling.
Extensive unit tests. Every module gets #[cfg(test)] coverage for happy paths, edge cases, and failures. Run cargo test before committing. If a task adds code, it adds tests.

Read the full file on GitHub · 137 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.

2mo ago First seen · 137 lines · 1,511 tokens per session scan A a3b18b255bc0

Subscribe to this mod's changes

batty CLAUDE.md is an instructions file published in the GitHub repository battysh/batty (60 stars, last pushed 2mo ago), licensed MIT. It adds 1,511 tokens to every session, about $0.0060 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.

Building agents Languages Rust agent-automation ai-agents cli developer-tools kanban

batty CLAUDE.md next to 6 instructions from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
batty CLAUDE.mdbattysh/batty	Instructions file	60	2mo ago	MIT	A	1,511	Claude Code
vscode buildNext.instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	9,719	GitHub Copilot
next.js AGENTS.mdvercel/next.js	Instructions file	143k	yesterday	MIT	A	7,461	Codex, OpenCode
langchain AGENTS.mdlangchain-ai/langchain	Instructions file	149k	yesterday	MIT	A	4,680	Codex, OpenCode
vscode oss-third-party-notices.instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	5,516	GitHub Copilot
vscode copilot-instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	3,093	GitHub Copilot
deepseek-harness AGENTS.mddeepseek-ai/deepseek-harness	Instructions file	274k	2d ago	MIT	A	4,313	Codex, OpenCode

batty: Instructions file for Claude Code