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.
git clone --depth 1 https://github.com/travisjneuman/.claudeWrote 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/travisjneuman/.claude/assemble-team)<a href="https://agentmods.dev/commands/travisjneuman/.claude/assemble-team"><img src="https://agentmods.dev/badge/commands/travisjneuman/.claude/assemble-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/travisjneuman/.claude/assemble-team"><img src="https://agentmods.dev/badge/commands/travisjneuman/.claude/assemble-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.00025 | $0.00853 |
| Opus 5.5 | $0.00010 | $0.00341 |
| Sonnet 5.5 | $0.00005 | $0.00171 |
| Haiku 4.5 | $0.00003 | $0.00085 |
Grade A, and why
assemble-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 26d 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 — 125 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/assemble-team Command
Assemble an agent team from pre-built templates or a custom description.
Agent teams are experimental and off by default. They only work in a session started with CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS=1; if the current session wasn't, say so and offer ordinary subagents instead.
Syntax
/assemble-team <template|description>
Templates
review - Full Code Review
/assemble-team review
Spawns 3 teammates for comprehensive PR/code review:
- Security reviewer: OWASP vulnerabilities, auth issues, input validation, secrets exposure
- Performance reviewer: N+1 queries, memory leaks, unnecessary re-renders, bundle impact
- Correctness reviewer: logic errors, edge cases, error paths, and callers affected by the diff
feature - Feature Development
/assemble-team feature [description]
Spawns 3 teammates for end-to-end feature development:
- Architect: designs approach, identifies files, plans dependencies (plan approval required)
- Implementer: writes code following the architect's approved plan
- Reviewer: reviews the implementation diff against the request and the code it touches (tests only if the user asks)
debug - Debug Squad
/assemble-team debug [problem description]
Spawns 3-5 teammates investigating competing hypotheses:
- Each teammate investigates a different theory
- Teammates challenge each other's findings
- Converges on root cause through adversarial debate
cross-platform - Mobile Parity
/assemble-team cross-platform [feature]
Spawns 3 teammates for mobile feature parity:
- iOS developer: Swift/SwiftUI implementation
- Android developer: Kotlin/Compose implementation
- Shared architect: API contracts, consistent behavior
fullstack - Full-Stack Development
/assemble-team fullstack [feature]
Spawns 3 teammates for cross-layer changes:
- Frontend: React/UI components
- Backend: API endpoints and services
- Database: schema, migrations, queries
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.
- 26d ago Changed · +3 lines 58d7bfe516a3
- 1mo ago First seen · 122 lines · 25 tokens per session scan A 2c972cf16412
assemble-team is a command published in the GitHub repository travisjneuman/.claude (106 stars, last pushed yesterday), licensed MIT. It adds 25 tokens to every session and 853 once invoked, about $0.0001 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-03.
Other commands, from other repositories
code-review
Review staged git changes for bugs, security issues, and style violations.
work-pr
Creates a complete and well-documented Pull Request.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.