What is council-sim CLAUDE.md?

A repository-specific instruction file for a simulator of city-council debates about proposed data centres. It describes a Python backend, a React and TypeScript frontend, and AI participants with different roles.

Use it when working on the simulator’s debate phases, participant personas, document analysis, live updates, or frontend and backend services.

It gives coding agents the project layout, design choices, and development conventions needed to make compatible changes.

How tony-42069/council-sim configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to tony-42069/council-sim. 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/tony-42069/council-sim/main/CLAUDE.md

Clone the repo

git clone --depth 1 https://github.com/tony-42069/council-sim

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/tony-42069/council-sim/claude-md/github.svg)](https://agentmods.dev/instructions/tony-42069/council-sim/claude-md)

Your own site

<a href="https://agentmods.dev/instructions/tony-42069/council-sim/claude-md"><img src="https://agentmods.dev/badge/instructions/tony-42069/council-sim/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/tony-42069/council-sim/claude-md"><img src="https://agentmods.dev/badge/instructions/tony-42069/council-sim/claude-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 870 This file is loaded in full into every session.

When invoked 870 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.00870	$0.00870
Opus 5	$0.00435	$0.00435
Sonnet 5	$0.00174	$0.00174
Haiku 4.5	$0.00087	$0.00087

Measured 9d ago against content hash 4b8d47a0c7a4, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

council-sim 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 9d 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 · 65 lines

How it starts

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

Council Simulator

Project Overview

AI-powered city council meeting simulator for data center proposal debates. Built for the "Built with Opus 4.6" Claude Code Hackathon (Cerebral Valley + Anthropic). Submission deadline: Feb 16, 3 PM EST.

Repo: https://github.com/tony-42069/council-simulator.git Local dir: D:\AI Projects\anthropic-hackathon (rename to council-simulator later)

Architecture

Backend: Python 3.10+ / FastAPI / Uvicorn (in backend/)
Frontend: React + TypeScript + Vite + Tailwind CSS (in frontend/)
AI - Agents: Claude Agent SDK for intelligence layer (persona gen, doc analysis, debate analysis)
AI - Debate: Anthropic Python SDK (anthropic) for streaming debate turns
Real-time: WebSockets for streaming debate to frontend
Deployment: Railway (backend) + Vercel (frontend)

Key Design Decisions

Hybrid AI approach: Agent SDK for autonomous research/analysis tasks, direct Anthropic API for debate turns (needs fine-grained streaming control)
5 debate phases: Opening → Public Comment → Rebuttal → Council Q&A → Deliberation
5 agent personas: Moderator, Petitioner, Concerned Parent, Environmental Activist, Property Owner
WebSocket message protocol: phase_change, persona_intro, speaking_start, token, speaking_end, analysis, complete, status, error
In-memory state only (no database)

Coding Conventions

Python: Use async/await throughout. Type hints on all functions. Pydantic models for data contracts.
TypeScript: Strict mode. Interfaces over types where possible. Use React hooks pattern.
Commits: One per task, descriptive message, always include Co-Authored-By line.
Branches: One per phase (e.g., phase-1/foundation). PR to merge each phase.

Git Workflow

Each phase = a git branch (phase-N/name)
Each task = a git commit within that branch
After all tasks in a phase → push → PR → merge to main
Always include: Co-Authored-By: Claude Opus 4.6 <[email protected]>

Important Files

IMPLEMENTATION_PLAN.md — Full architecture and design doc
PHASES_AND_TASKS.md — Detailed phase/task breakdown with commit messages
ANTHROPIC_DATA_CENTER_ANNOUNCEMENT.md — Real-world data to integrate into petitioner agent

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

9d ago First seen · 65 lines · 870 tokens per session scan A 4b8d47a0c7a4

Subscribe to this mod's changes

council-sim CLAUDE.md is an instructions file published in the GitHub repository tony-42069/council-sim (3 stars, last pushed 6mo ago), licensed MIT. It adds 870 tokens to every session, about $0.0043 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.

Claude Code anthropic claude-agent-sdk claude-opus-4-6 claude-skills hackathon

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,296 tokens

codex AGENTS.md

AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.

openai/codex · 5,153 tokens

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 · 6,785 tokens

council-sim: Instructions file for Claude Code