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.
npx agentmods add commands/xyzbit/claude-plugins/architect-phase-workflowgit clone --depth 1 https://github.com/xyzbit/claude-pluginsWhat 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 | $0.00028 | $0.02217 |
| Opus 5 | $0.00014 | $0.01108 |
| Sonnet 5 | $0.00006 | $0.00443 |
| Haiku 4.5 | $0.00003 | $0.00222 |
Grade A, and why
architect:phase-workflow 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 3d 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 — 362 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/architect:phase-workflow
This command provides comprehensive phase management for the Senior Architect Collaboration workflow. It can start a new phase with templates, validate phase completion criteria, or generate phase-specific documentation.
Usage
Interactive Mode (Recommended)
/architect:phase-workflow
Prompts will guide you through phase selection, project setup, and actions.
Automated Mode
/architect:phase-workflow --phase 1 --project "E-commerce Platform" --generate
Arguments
-
--phase <number>: Phase number (1-4)- 1: Requirements Analysis
- 2: Technical Design
- 3: Task Breakdown
- 4: Feature Development
-
--project <name>: Project name for documentation -
--interactive: Force interactive mode (default if no other flags) -
--generate: Generate phase templates only -
--validate: Validate phase completion only -
--help: Show help information
Examples
Example 1: Start New Phase (Interactive)
/architect:phase-workflow
Output:
🚀 Architect Collaboration - Phase Workflow
Select phase:
1. Requirements Analysis
2. Technical Design
3. Task Breakdown
4. Feature Development
Enter choice (1-4): 2
Selected: Phase 2 - Technical Design
Project name: User Authentication System
What would you like to do?
[1] Generate templates and start phase
[2] Validate existing phase work
[3] Both generate and validate
Select option (1-3): 1
✅ Created: docs/technical-design.md
✅ Created: docs/architecture-diagram.md
✅ Created: docs/pseudocode.md
Phase 2 started successfully!
Next steps:
1. Review generated templates
2. Use Requirements Analysis Skill to gather requirements
3. Use Technical Design Skill for solution architecture
Example 2: Generate Templates Only
/architect:phase-workflow --phase 3 --project "Payment Gateway" --generate
Output:
📋 Generating templates for Phase 3: Task Breakdown
✅ Created: docs/开发任务.md
✅ Created: docs/task-dependencies.md
✅ Created: docs/sprint-plan.md
Templates generated successfully!
Location: docs/
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.
- 3d ago First seen · 362 lines · 28 tokens per session scan A c5fb41e3040d
architect:phase-workflow is a command published in the GitHub repository xyzbit/claude-plugins (27 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 28 tokens to every session and 2,217 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
git
Git operations with intelligent commit messages and workflow optimization.
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.