Borrowing it
Nothing to install: this file belongs to Tenon-Net/Agent-Team. 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/Tenon-Net/Agent-Team/main/AGENTS.mdgit clone --depth 1 https://github.com/Tenon-Net/Agent-TeamWrote 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/tenon-net/agent-team/agents-md)<a href="https://agentmods.dev/instructions/tenon-net/agent-team/agents-md"><img src="https://agentmods.dev/badge/instructions/tenon-net/agent-team/agents-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.
<a href="https://agentmods.dev/instructions/tenon-net/agent-team/agents-md"><img src="https://agentmods.dev/badge/instructions/tenon-net/agent-team/agents-md.svg" alt="Reviewed on agentmods" width="80" 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.01270 | $0.01270 |
| Opus 5.5 | $0.00508 | $0.00508 |
| Sonnet 5.5 | $0.00254 | $0.00254 |
| Haiku 4.5 | $0.00127 | $0.00127 |
Grade A, and why
Agent-Team AGENTS.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 2mo 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.
How it starts
The opening of the file, as written. The whole thing — 114 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent-Team
Purpose
Claude Code plugin that implements a single-brain multi-agent coding
pipeline: Claude plans and judges; an Executor (grok or codex)
implements tasks in git worktrees; codex reviews read-only; Claude
merges and reports. This repository is the plugin source (marketplace +
skill + harness scripts), not a sample application.
Current version: read .claude-plugin/plugin.json → version (do not
hardcode elsewhere without updating the release checklist).
Map
| Path | Role |
|---|---|
.claude-plugin/ |
Marketplace + plugin manifest (version is the upgrade signal) — see .claude-plugin/AGENTS.md |
commands/ |
Claude Code slash-command entry (/agent-team) |
skills/agent-team/ |
Orchestration skill, schemas, ADRs, Phase findings — see skills/agent-team/AGENTS.md |
scripts/ |
Headless harness: executor / reviewer / resolve — see scripts/AGENTS.md |
README.md / README.zh-CN.md |
Human install, update, usage |
CHANGELOG.md |
Release notes by semver |
CLAUDE.md |
Claude-specific maintainer workflow (release, sessions) |
LICENSE |
MIT |
Architecture (one screen)
User → /agent-team → Claude (Brain)
│
plan.md approval + state.json under target repo .agentteam/
│
per task: worktree → run-executor.mjs → run-reviewer.mjs
│
trust+gate → commit/merge → report
| Role | Who | Writable? |
|---|---|---|
| Brain | Claude in Claude Code | worktrees/commits/judgement; no silent self-review exemption |
| Executor | grok or codex (auto prefers grok) |
only its worktree (+ result dir for codex via --add-dir) |
| Reviewer | always codex |
no (--sandbox read-only) |
Roles ≠ product names. Design intent and hard-won CLI facts:
skills/agent-team/docs/CONTEXT.md and docs/adr/.
Invariants (do not violate without an ADR)
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.
- 2mo ago First seen · 114 lines · 1,270 tokens per session scan A 1cff1c8667c5
Agent-Team AGENTS.md is an instructions file published in the GitHub repository Tenon-Net/Agent-Team (2 stars, last pushed 2mo ago), licensed MIT. It adds 1,270 tokens to every session, about $0.0051 per session on Opus 5.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).
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.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
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 copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deno copilot-instructions.md
Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.