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/bostonaholic/team/agents-mdgit clone --depth 1 https://github.com/bostonaholic/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/bostonaholic/team/agents-md)<a href="https://agentmods.dev/instructions/bostonaholic/team/agents-md"><img src="https://agentmods.dev/badge/instructions/bostonaholic/team/agents-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.03923 | $0.03923 |
| Opus 5 | $0.01962 | $0.01962 |
| Sonnet 5 | $0.00785 | $0.00785 |
| Haiku 4.5 | $0.00392 | $0.00392 |
Grade A, and why
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 today.
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 — 116 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md: Project Router
This file is a table of contents, not an encyclopedia. Keep it under ~150 lines. Point agents to references. Do not embed content here. If guidance needs to exist, put it in
docs/and link from here.
What this is
Team is a Claude Code plugin that orchestrates specialized agents to implement features end-to-end. The orchestrator (the main Claude Code session) walks a linear phase table, and persists state as artifact files in docs/plans/<id>/. That per-id directory carries YAML frontmatter with phase and revision metadata. The orchestrator coordinates live progress through TodoWrite. See docs/architecture.md for the full design.
North star: read docs/vision.md and docs/ethos.md. Team is a loop-driven development system: a human fills the Backlog and reviews finished work. Everything in between (groom → start → implement → open PR) runs autonomously. The ethos explains why the autonomous middle can be trusted. Every agent should understand this end state, which is the target the whole project moves toward.
Runtime vs. development
This project produces a distributed plugin. Two contexts exist:
Runtime (agents/, skills/, hooks/, and the host manifests .claude-plugin/, .codex-plugin/, .agents/plugins/, and the root plugin.json) ships to end users. Fires when someone installs the Team plugin and runs /team. Changes here affect all users.
Development (.claude/) is our workspace tooling. Fires only when developing the plugin itself. Never distributed.
| Concern | Where it lives | Who runs it |
|---|---|---|
| Pipeline agents, skills, hooks | agents/, skills/, hooks/ |
End users |
| Plugin manifests | .claude-plugin/ (Claude Code), .codex-plugin/ + .agents/plugins/ (Codex), root plugin.json (Antigravity) |
End users |
| Registry sync validation | .claude/hooks/check-registry-sync.mjs |
Plugin developers |
| Pre-merge version gate | .claude/hooks/pre-merge-guard.mjs |
Plugin developers |
| Dev acceptance scripts | .claude/scripts/ |
Plugin developers |
| Dev settings/hooks | .claude/settings.json |
Plugin developers |
| Work tracking | GitHub Project board | Plugin developers |
| Behavioral regression harness | tests/, evals/ |
Plugin developers |
| Versioning & release automation | docs/versioning.md, .claude/skills/version-bump/, .claude/scripts/next-version.sh, .github/workflows/ |
Plugin developers |
| Dev install, per harness | script/dev-install/dev-uninstall (dispatch), dev-install-<harness> |
Plugin developers |
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.
- today Changed · +410 tokens per session 7134a4f63a07
- 3d ago First seen · 116 lines · 3,513 tokens per session scan A 628a0497ee0e
team AGENTS.md is an instructions file published in the GitHub repository bostonaholic/team (11 stars, last pushed today), licensed MIT. It adds 3,923 tokens to every session, about $0.0196 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.
Other instructions, from other repositories
tutti AGENTS.md
AGENTS.md instructions for tutti-os/tutti, covering agents.md, shape, routing, agent host boundary and contribution workflow.
babysitter AGENTS.md
AGENTS.md instructions for a5c-ai/babysitter, covering agents.md, repo-specific overrides, reference map and quick commands.
babysitter CLAUDE.md
Claude Code instructions for a5c-ai/babysitter, covering claude.md, repo-specific overrides, read these first, quick commands and claude code local notes.
work-buddy CLAUDE.md
Claude Code instructions for KadenMc/work-buddy, covering work buddy, mcp gateway, capability vs workflow, workflow consent (composable) and session init (mandatory).
mavericks-os CLAUDE.md
Claude Code instructions for yahor-punko/mavericks-os, covering claude.md, what this repo is, session start, operational commands and architecture.
Formic CLAUDE.md
Instructions for rickywo/Formic, covering formic task manager assistant, your capabilities, what you can do, what you cannot do and core behavioral rules.