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/rhuss/cc-spexWrote 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/rhuss/cc-spex/speckit.spex-teams.orchestrate)<a href="https://agentmods.dev/commands/rhuss/cc-spex/speckit.spex-teams.orchestrate"><img src="https://agentmods.dev/badge/commands/rhuss/cc-spex/speckit.spex-teams.orchestrate/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/rhuss/cc-spex/speckit.spex-teams.orchestrate"><img src="https://agentmods.dev/badge/commands/rhuss/cc-spex/speckit.spex-teams.orchestrate.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.00018 | $0.01591 |
| Opus 5 | $0.00009 | $0.00796 |
| Sonnet 5 | $0.00004 | $0.00318 |
| Haiku 4.5 | $0.00002 | $0.00159 |
Grade A, and why
speckit.spex-teams.orchestrate 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 10d 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 — 161 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Teams Orchestration: Parallel Task Implementation
Overview
This command orchestrates parallel task implementation using Claude Code Agent Teams. The lead session analyzes the task dependency graph, spawns teammates in isolated worktrees for independent task groups, reviews all changes against spec.md via the spec guardian pattern, and coordinates merges. The spec guardian review loop is always-on: every teammate's work is reviewed for spec compliance before merging.
Prerequisites
CC Teams Feature Flag
Check if Agent Teams is enabled:
# Check settings.local.json for the feature flag
FLAG=$(jq -r '.env.CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS // ""' .claude/settings.local.json 2>/dev/null)
If the flag is not set ("" or missing):
- Set it in
.claude/settings.local.json:jq '.env.CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS = "1"' .claude/settings.local.json > /tmp/settings.json && mv /tmp/settings.json .claude/settings.local.json - Inform the user: "Agent Teams feature flag has been enabled. Please restart Claude Code for teams to activate."
- Fall back to sequential implementation for this session (teams will work on next run).
If the flag is set: Proceed with team orchestration.
If the flag becomes unset mid-session (e.g., user restarts without it): The pre-flight check runs at skill invocation time, not continuously. If the env var disappears mid-session, already-spawned teammates continue working. On next invocation, the check will catch the missing flag and fall back to sequential.
Task Graph Analysis
Read the tasks.md file and analyze the dependency structure:
- Parse all tasks with their IDs, descriptions, and phase membership
- Identify dependency relationships from the Dependencies section and phase ordering
- Group tasks by independence: tasks that can execute simultaneously (no shared dependencies, different files)
- Identify blocked tasks: tasks that must wait for others to complete first
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.
- 10d ago First seen · 161 lines · 18 tokens per session scan A 0e597e801a17
speckit.spex-teams.orchestrate is a command published in the GitHub repository rhuss/cc-spex (116 stars, last pushed 21d ago), licensed Apache-2.0. It adds 18 tokens to every session and 1,591 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-30.
Other commands, from other repositories
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.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
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.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.