Borrowing it
Nothing to install: this file belongs to prebid/salesagent. 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/prebid/salesagent/main/.claude/commands/team.mdgit clone --depth 1 https://github.com/prebid/salesagentWrote 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/commands/prebid/salesagent/team)<a href="https://agentmods.dev/commands/prebid/salesagent/team"><img src="https://agentmods.dev/badge/commands/prebid/salesagent/team/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/commands/prebid/salesagent/team"><img src="https://agentmods.dev/badge/commands/prebid/salesagent/team.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.00012 | $0.02120 |
| Opus 5.5 | $0.00005 | $0.00848 |
| Sonnet 5.5 | $0.00002 | $0.00424 |
| Haiku 4.5 | $0.00001 | $0.00212 |
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 1mo 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 — 205 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Launch Agent Team: $ARGUMENTS
MANDATORY: Worktree-isolated executors (no team_name)
For any spawn that creates N ≥ 2 concurrent executors, EACH spawn MUST use:
subagent_type: "executor"(.claude/agents/executor.md)isolation: "worktree"— the Claude Code harness primitiverun_in_background: true— so all executors run concurrently- NO
team_name/ NOTeamCreate. Combiningteam_name(theCLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMSpath) withisolation: "worktree"is silently downgraded by the harness: the executor is routed to the team coordination context and runs on the shared main working copy instead of an isolated worktree. This was observed first-hand (parallel executors clobberingsrc/app.py, a tree-widegit stashswallowing a sibling's uncommitted files).team_nameis prohibited for parallel execution.
Coordinate via the agentId returned by each spawn (SendMessage accepts
the agentId as to) and the harness's automatic <task-notification> on
completion. Do NOT use TeamCreate, TaskCreate, or SendMessage-by-name.
Solo spawns (N = 1) MAY run on the main working copy and skip
isolation: "worktree".
Protocol
Step 0: Resolve the team-lead HEAD SHA (binding)
Before any spawn, from the main repo root:
git rev-parse HEAD
Capture the full 40-char SHA. The harness allocates each worktree's branch from the default branch tip, not from the team-lead's HEAD — so an executor's worktree can start on a stale base. Thread this SHA literally into every executor prompt; the executor resets to it on entry (see Step 2).
Step 1: Provision ONE shared Postgres for the wave
Worktree-isolated executors each have their own working copy but
agent-db.sh derives its container name from .claude/skills (constant
across worktrees), so per-executor agent-db instances collide. Instead the
team-lead brings up ONE shared Postgres and threads its DATABASE_URL into
every executor prompt. The integration_db fixture creates a unique
database per test, so a single server is safe under concurrency.
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.
- 1mo ago Changed · +2 lines 573d715fdcd0
- 1mo ago First seen · 203 lines · 12 tokens per session scan A 52ca287a22ef
team is a command published in the GitHub repository prebid/salesagent (39 stars, last pushed yesterday), licensed Apache-2.0. It adds 12 tokens to every session and 2,120 once invoked, about $0.0000 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-09-01.
Other commands, from other repositories
template
Manage issue templates for streamlined issue creation.
fest-show
Show festival progression (in-progress tasks, roadmap, and dependency view).
add-note
Add an internal or external note to a ConnectWise PSA ticket.
dispatcher
Use when you want the orchestrator to pick the next repo to work on across your whole portfolio — it enumerates candidate repos below the confinement root, resolves free/busy from each repo's session.lock lease, ranks the FREE ones by backlog priority × staleness × readiness, recommends the single most worthwhile one…
sync-linear
Sync current work with Linear ticket status.
workpm
A project-management workflow for coordinating multiple AI workers through five stages. It includes task assignment, shared activity logs, worker replacement, and final checks.