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-collab.phase-manager)<a href="https://agentmods.dev/commands/rhuss/cc-spex/speckit.spex-collab.phase-manager"><img src="https://agentmods.dev/badge/commands/rhuss/cc-spex/speckit.spex-collab.phase-manager/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-collab.phase-manager"><img src="https://agentmods.dev/badge/commands/rhuss/cc-spex/speckit.spex-collab.phase-manager.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.00015 | $0.04441 |
| Opus 5 | $0.00008 | $0.02220 |
| Sonnet 5 | $0.00003 | $0.00888 |
| Haiku 4.5 | $0.00002 | $0.00444 |
Grade A, and why
speckit.spex-collab.phase-manager 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 9d 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 — 489 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Phase Manager
Coordinates the boundary between implementation phases: runs code review, updates REVIEWERS.md with code-specific guidance, offers PR creation, and manages phase state for cross-session continuity.
Script References
FLOW_STATE=".specify/extensions/spex-collab/scripts/spex-flow-state.sh"
Ship Pipeline Guard
if [ -f ".specify/.spex-state" ]; then
MODE=$(jq -r '.mode // empty' .specify/.spex-state 2>/dev/null)
STATUS=$(jq -r '.status // empty' .specify/.spex-state 2>/dev/null)
if [ "$MODE" = "ship" ] || [ "$STATUS" = "running" ]; then
echo "Ship mode active, skipping phase manager"
fi
fi
If ship mode is detected, return immediately.
Extension Enabled Check
if [ ! -f ".specify/extensions/spex-collab/extension.yml" ]; then
echo "spex-collab extension not found, skipping"
fi
If the extension is not found, return without action.
Read Phase State
Load the phase plan and completion state from .specify/.spex-state:
PHASE_PLAN=$(jq -r '.collab.phase_plan // empty' .specify/.spex-state 2>/dev/null)
COMPLETED=$(jq -r '.collab.completed_phases // []' .specify/.spex-state 2>/dev/null)
PR_BASE=$(jq -r '.collab.pr_base_branch // "main"' .specify/.spex-state 2>/dev/null)
If no phase plan exists (collab.phase_plan is empty or missing):
- Output: "No phase plan found. Run the phase-split command first, or invoke
/speckit.spex-collab.phase-splitto create one." - Return.
Single-Phase Detection
Check if the phase plan contains exactly one entry, indicating single-phase mode (either threshold-defaulted or user-selected):
PHASE_COUNT=$(jq '.collab.phase_plan | length' .specify/.spex-state 2>/dev/null || echo "0")
If PHASE_COUNT equals 1, this is a single-phase implementation. In single-phase mode:
- This invocation is the final and only phase-manager call
- It happens after all tasks have been completed
- Skip any "next phase" logic; proceed directly to the review gate, REVIEWERS.md update, and PR offer
- When displaying the phase, indicate single-phase mode: "Phase 1: Full Implementation (single phase)"
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.
- 9d ago First seen · 489 lines · 15 tokens per session scan A 0684cf268e12
speckit.spex-collab.phase-manager is a command published in the GitHub repository rhuss/cc-spex (116 stars, last pushed 20d ago), licensed Apache-2.0. It adds 15 tokens to every session and 4,441 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
land
Cadence-tick autonomous PR babysitter (CI-fix, resolve, converge, merge, close, release).
sync
Synchronizes your local swarm state with the latest GitHub repository state, updating task statuses and detecting changes.
claim
Claims a GitHub issue for your swarm to work on, preventing conflicts with other swarms.
weekly-summary
Generate weekly work summary from git activity.
next
Suggest the most likely next workflow action based on current context.
update-check.template
This prompt was authored for Claude-style slash workflows. In Codex runtime, adapt tool calls as follows.