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/richardlemmon/agentteam/claude-mdgit clone --depth 1 https://github.com/RichardLemmon/AgentTeamWrote 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/richardlemmon/agentteam/claude-md)<a href="https://agentmods.dev/instructions/richardlemmon/agentteam/claude-md"><img src="https://agentmods.dev/badge/instructions/richardlemmon/agentteam/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 | $0.00241 | $0.00241 |
| Opus 5 | $0.00120 | $0.00120 |
| Sonnet 5 | $0.00048 | $0.00048 |
| Haiku 4.5 | $0.00024 | $0.00024 |
Grade A, and why
AgentTeam 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 3d 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
AgentTeam — How to Use
When the user asks to spin up a team, build something with the team, or use AgentTeam:
- Read
agents/project-manager.mdfrom this repository - Spawn the PM agent with the user's goal as the task
- The PM will return a
## DISPATCH_MANIFESTJSON block at the end of its response - For each entry in the manifest:
- If
agent_prompt_fileis set: read that file for the agent's prompt - If
agent_promptis set: use the inline prompt (ad-hoc specialist) - Spawn the specialist with their
project_id,member_id, and tasks - Tell each specialist to call
get_team_protocolfirst to load the shared team protocol
- If
- Run specialists in parallel
- After completion, call
list_user_questionswithstatus=pending— if any exist, present them to the user and write answers back viaanswer_user_question - Check
list_expansion_requestswithstatus=pending— if any exist, re-run the PM to evaluate and dispatch approved expansions
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.
- 3d ago First seen · 16 lines · 241 tokens per session scan A 2f21ef370666
AgentTeam CLAUDE.md is an instructions file published in the GitHub repository RichardLemmon/AgentTeam (0 stars, last pushed 4mo ago), licensed MIT. It adds 241 tokens to every session, about $0.0012 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
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).
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.
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.