team

A command for managing feature development through seven phases, with work shared across multiple agents and approval points for the user.

In plain words
What is it for?
It is for planning, building, reviewing, and completing software features with parallel agent work and user checkpoints.
Why use it?
It provides a defined process for taking a feature from planning to implementation instead of handling each step ad hoc.

Command

Install

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.

agentmods
npx agentmods add commands/andvl1/claude-plugin/team
Clone the repo
git clone --depth 1 https://github.com/AndVl1/claude-plugin
Per session 16 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 10,451 The whole file, excluding the scripts and references it only reads on demand.
Security scan B 2 findings. Scan, not verified.
Origin unknown 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 $0.00016 $0.10451
Opus 5 $0.00008 $0.05226
Sonnet 5 $0.00003 $0.02090
Haiku 4.5 $0.00002 $0.01045

Measured 2d ago against content hash a6e57accad01, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade B, and why

team scanned grade B with 2 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.

Reads agent configuration directoriesmediumAgent snooping

.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.

> **Backward compatibility**: In earlier versions, state files were stored in `.claude/`. If you find `team-state.md` in `.claude/` from a previous session, continue working with it there — but for **new sessions always

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

- You're about to ssh/curl prod, query a DB, run a build/test, or reproduce a bug.
commands/team.md · 833 lines

The source is not reproduced here

No licence file

A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.

Read it on GitHub

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. 2d ago First seen · 833 lines · 16 tokens per session scan B a6e57accad01

Subscribe to this mod's changes

team is a command published in the GitHub repository AndVl1/claude-plugin (4 stars, last pushed 1mo ago), with no licence file. It adds 16 tokens to every session and 10,451 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it B with 2 findings (reads agent configuration directories, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.