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 instructions/oitapps/claude-code-team-commander/claude-mdgit clone --depth 1 https://github.com/OITApps/claude-code-team-commanderWhat 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 | $0.00273 | $0.00273 |
| Opus 5 | $0.00137 | $0.00137 |
| Sonnet 5 | $0.00055 | $0.00055 |
| Haiku 4.5 | $0.00027 | $0.00027 |
Grade A, and why
claude-code-team-commander 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 2d 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.
What it actually says
CLAUDE.md -- claude-code-team-commander
Overview
Public blueprint and playbook for building a shared Claude Code configuration for a team or company. Not a runtime server -- this repo contains documentation, example configs, and setup/audit scripts. Published by OIT, LLC.
Structure
blueprint.md-- complete system prompt for building your own team configscripts/audit/-- audit toolingexamples/-- example configurationsexample-catalog.json-- sample approved tool catalogexample-announcements.json-- sample team announcement payloadsexample-CLAUDE.md-- template project-level CLAUDE.mdexample-team-announcement.md-- sample announcement format
Usage
No build step. This is a reference repo. Teams clone it, customize blueprint.md with their org details, and use the generated scripts (setup.sh, catalog.sh, bootstrap-repo.sh) in their own config repo.
Secrets
- No secrets in this repo -- it is public
- The generated setup scripts prompt users for API keys at install time
- Generated
.mcp.jsonand.envfiles are gitignored by design - Teams should use their own secret management (Azure Key Vault, etc.)
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.
- 2d ago First seen · 27 lines · 273 tokens per session scan A 4391b4915c56
claude-code-team-commander CLAUDE.md is an instructions file published in the GitHub repository OITApps/claude-code-team-commander (7 stars, last pushed 3mo ago), licensed MIT. It adds 273 tokens to every session, about $0.0014 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 instructions, from other repositories
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.
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).
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.
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).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.