team

A command for coordinating several specialized coding agents on one project. The agents can review code, assess security, design architecture, write tests, inspect deployment, or evaluate user interfaces.

In plain words
What is it for?
Use it for review, architecture, release readiness, quality checks, documentation, or a custom group of selected agents.
Why use it?
It divides a broad review or implementation task into focused checks that can run in parallel.

Skill for Claude CodeCodex

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 skills/bostonorange/claude-code-framework/team
Any agent
npx skills add BostonOrange/claude-code-framework --skill team
Clone the repo
git clone --depth 1 https://github.com/BostonOrange/claude-code-framework

Made for: Claude Code, Codex.

Per session 17 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 925 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original 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.00017 $0.00925
Opus 5 $0.00009 $0.00463
Sonnet 5 $0.00003 $0.00185
Haiku 4.5 $0.00002 $0.00093

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

Security

Grade A, and why

team 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 yesterday.

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.

.agents/skills/team/SKILL.md · 106 lines

How it starts

The opening of the file, as written. The whole thing — 106 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Team — Agent Group Orchestration

Spawn a team of specialized agents to work in parallel on the current codebase.

Usage

/team review          — Code reviewer + Security auditor + UI/UX reviewer
/team architecture    — Architect + API designer + Database architect
/team release         — Security auditor + DevOps engineer + Performance optimizer
/team quality         — Code reviewer + Test writer + Performance optimizer
/team documentation   — Documentation writer + API designer
/team full            — All 10 review/implementation agents (excludes meta-agents)
/team custom agent1 agent2 agent3   — Pick specific agents

Available Agents

Agent Role Model Tools
architect System design, patterns, structural risks opus Read-only
code-reviewer Bugs, security, performance in diff opus Read-only
security-auditor OWASP audit, credentials, dependencies opus Read-only
test-writer Generate tests for changed code opus Read/Write
devops-engineer CI/CD, infra, deployment readiness opus Read-only
ui-ux-reviewer Accessibility, design, responsiveness opus Read-only
performance-optimizer Bundle, queries, rendering, caching opus Read-only
documentation-writer API docs, READMEs, architecture docs opus Read/Write
api-designer Endpoint design, schemas, consistency opus Read-only
database-architect Schema, migrations, indexes, queries opus Read-only
framework-improver Self-improvement of .codex/ config (invoked by /improve, not /team) opus Read/Write

Process

Phase 1: Parse Team Request

Parse the team name from the command argument. Map to agent list:

Team Agents
review code-reviewer, security-auditor, ui-ux-reviewer
architecture architect, api-designer, database-architect
release security-auditor, devops-engineer, performance-optimizer
quality code-reviewer, test-writer, performance-optimizer
documentation documentation-writer, api-designer
full all 10 review/implementation agents (excludes framework-improver)
custom agents listed after "custom" keyword

Read the full file on GitHub · 106 lines

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. yesterday First seen · 106 lines · 17 tokens per session scan A fbbbcdffd83b

Subscribe to this mod's changes

team is a skill published in the GitHub repository BostonOrange/claude-code-framework (2 stars, last pushed 1mo ago), licensed MIT. It adds 17 tokens to every session and 925 once invoked, about $0.0001 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.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

brainstorming

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

obra/superpowers · 37 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

babysit-pr

Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…

openai/codex · 114 tokens

imagegen

Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…

openai/codex · 113 tokens