ClaudeTeam: Instructions file for Claude Code

CLAUDE.md

ClaudeTeam CLAUDE.md is an instructions file for Claude Code from zylMozart/ClaudeTeam. It costs 1,987 tokens per session, scanned A, original, MIT.

Repository instructions for Claude Code, an AI coding assistant, explaining the project layout, development rules, and required checks.

In plain words
What is it for?
Use them when adding or changing Python commands, local state, runtime code, integrations, agent adapters, or tests in this repository.
Why use it?
They give the assistant a reliable map of the codebase and prevent changes from skipping tests, simplicity checks, or deployment guidance.

Instructions file for Claude Code

Written for Claude Code: the file is CLAUDE.md. Also seen: mentions CLAUDE.md; mentions Claude Code; mentions Codex.

This is zylMozart/ClaudeTeam's own configuration. It tells Claude Code how to work on ClaudeTeam itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything ClaudeTeam configures →

Reuse

Borrowing it

Nothing to install: this file belongs to zylMozart/ClaudeTeam. 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/zylMozart/ClaudeTeam/main/CLAUDE.md
Clone the repo
git clone --depth 1 https://github.com/zylMozart/ClaudeTeam

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.

agentmods badge for ClaudeTeam CLAUDE.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/zylmozart/claudeteam/claude-md/github.svg)](https://agentmods.dev/instructions/zylmozart/claudeteam/claude-md)
Your own site
<a href="https://agentmods.dev/instructions/zylmozart/claudeteam/claude-md"><img src="https://agentmods.dev/badge/instructions/zylmozart/claudeteam/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.

agentmods 80×15 button for ClaudeTeam CLAUDE.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/zylmozart/claudeteam/claude-md"><img src="https://agentmods.dev/badge/instructions/zylmozart/claudeteam/claude-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 1,987 This file is loaded in full into every session.
When invoked 1,987 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.01987 $0.01987
Opus 5 $0.00993 $0.00993
Sonnet 5 $0.00397 $0.00397
Haiku 4.5 $0.00199 $0.00199

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

Security

Grade A, and why

ClaudeTeam 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 10d 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 · 161 lines

How it starts

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

Working in this repo (Claude Code context)

Read this file before making changes. See README.md for what the project is and how a user runs it.

For deployment (host or Docker), follow docs/DEPLOYMENT.md.

Where things live

Business logic lives in src/claudeteam/ only. There is no parallel scripts/ shim layer. Every command is a Python module under src/claudeteam/commands/ registered in src/claudeteam/cli.py.

src/claudeteam/cli.py           ← top-level dispatch + COMMANDS registry
src/claudeteam/commands/X.py    ← one module per subcommand, ~30 LOC each
src/claudeteam/store/           ← file-backed local state (no DB)
src/claudeteam/runtime/         ← config / paths / tmux / watchdog
src/claudeteam/feishu/          ← lark-cli wrapper + router pipeline
src/claudeteam/agents/          ← CliAdapter base + per-CLI adapters

Tests are in tests/unit/test_*.py (per-module), tests/integration/test_*.py (end-to-end in-process; auto gate), and tests/scenarios/*.md (operator-run regression playbooks).

Building rules (READ BEFORE WRITING CODE)

  1. Every new module ships its own unit test in the same commit. Touching commands/X.py? Write tests/unit/test_commands_X.py.

  2. Every new public command ships an operator playbook (markdown) in tests/scenarios/ in the same commit. Given/When/Then template, for human regression checks against a real deployment.

  3. Keep it small. Prefer the smallest thing that works — avoid speculative CliCapabilities-style dataclasses or deeply decomposed multi-file trees. If a function looks too short to need its own file, it probably is.

  4. No compatibility wrappers. Don't keep a shim around just because an old call site might break — update the call site instead.

  5. Test fixtures live in tests/helpers.py. Use isolated_env() and run_cli(). Don't copy-paste a new _isolated_state() per test file.

Simplicity gate (read before opening a PR)

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

  1. 10d ago First seen · 161 lines · 1,987 tokens per session scan A 3d3641841c33

Subscribe to this mod's changes

ClaudeTeam CLAUDE.md is an instructions file published in the GitHub repository zylMozart/ClaudeTeam (232 stars, last pushed 1mo ago), licensed MIT. It adds 1,987 tokens to every session, about $0.0099 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-30.

Related

Other instructions, from other repositories

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

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.

github/spec-kit · 7,104 tokens

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

microsoft/vscode · 5,001 tokens

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.

langchain-ai/langchain · 4,469 tokens