Borrowing it
Nothing to install: this file belongs to tonone-ai/tonone. 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/tonone-ai/tonone/main/CLAUDE.mdgit clone --depth 1 https://github.com/tonone-ai/tononeWrote 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/tonone-ai/tonone/claude-md)<a href="https://agentmods.dev/instructions/tonone-ai/tonone/claude-md"><img src="https://agentmods.dev/badge/instructions/tonone-ai/tonone/claude-md.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.03705 | $0.03705 |
| Opus 5 | $0.01852 | $0.01852 |
| Sonnet 5 | $0.00741 | $0.00741 |
| Haiku 4.5 | $0.00370 | $0.00370 |
Grade B, and why
tonone CLAUDE.md scanned grade B with 1 finding 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
- shell: find . -name "setup.sh" -not -path "./.git/*" -not -path "./.claude/*" | xargs shellcheck -S warning How it starts
The opening of the file, as written. The whole thing — 248 lines — stays where its author put it; the contents beside it link to each section on GitHub.
tonone — Engineering + Product + Operations + Legal + Design + Data Science + Security Operations + Developer Experience + Infrastructure Specialist + AI Operations Team
Ten AI teams. 100 agents total. Engineering executes. Product decides what to build and why. Operations keeps the company running. Legal de-risks every move. Design makes it beautiful and accessible. Data Science turns data into decisions. Security Operations keeps everything safe. Developer Experience ensures developers succeed. Infrastructure Specialist runs the cloud. AI Operations ships models to production.
Read docs/repomap.md first — this repo is too big to crawl by hand (100 agents, 405 skills). It points to docs/agent-index.json and docs/skill-index.json for lookups, and lists known content drift to watch for.
Engineering Team — 15 agents
| Agent | Hat | Owns |
|---|---|---|
| Apex | Engineering Lead | Orchestrates the team, scopes work, controls depth and budget |
| Forge | Infrastructure | Cloud services, networking, IaC, cost optimization |
| Relay | DevOps | CI/CD, deployments, GitOps, developer experience |
| Spine | Backend | APIs, system design, performance, distributed systems |
| Flux | Data | Databases, migrations, pipelines, data modeling |
| Warden | Security | IAM, secrets, compliance, threat modeling |
| Vigil | Observability + Reliability | Monitoring, alerting, SRE, incident response, SLOs |
| Prism | Frontend/DX | UI, internal tools, developer portals |
| Cortex | ML/AI | Model training, MLOps, feature engineering, LLM integration |
| Touch | Mobile | Native iOS/Android, cross-platform, app stores |
| Volt | Embedded/IoT | Firmware, microcontrollers, edge computing, protocols |
| Atlas | Knowledge Engineering | Architecture docs, ADRs, API specs, system diagrams |
| Lens | Data Analytics & BI | Dashboards, metrics design, reporting, data storytelling |
| Proof | QA & Testing | Test strategy, E2E suites, integration testing, flaky triage |
| Pave | Platform Engineering | Developer experience, golden paths, service catalogs |
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 · 248 lines · 3,705 tokens per session scan B d85b2d48f864
tonone CLAUDE.md is an instructions file published in the GitHub repository tonone-ai/tonone (71 stars, last pushed 21d ago), licensed MIT. It adds 3,705 tokens to every session, about $0.0185 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-01.
Other instructions, from other repositories
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.
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.
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 oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.