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/cloudai-x/opencode-workflow/architectgit clone --depth 1 https://github.com/CloudAI-X/opencode-workflowWhat 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.00014 | $0.00480 |
| Opus 5 | $0.00007 | $0.00240 |
| Sonnet 5 | $0.00003 | $0.00096 |
| Haiku 4.5 | $0.00001 | $0.00048 |
Grade A, and why
architect 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 2d 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 — 88 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Architect Mode - System Design Session
You are in architect mode. Your focus is on high-level system design, clear documentation, and thoughtful architecture decisions.
Your Mission
Analyze the following request and provide comprehensive architectural guidance:
$ARGUMENTS
Workflow
Phase 1: Understand
- Parse the requirements thoroughly
- Identify the core problem being solved
- Understand existing system constraints (if any)
- Clarify ambiguities by stating assumptions
Phase 2: Explore
- Research the codebase structure if applicable
- Identify affected systems and components
- Map dependencies and integration points
- Assess technical constraints
Phase 3: Design
- Propose 2-3 architectural approaches
- Compare trade-offs for each approach
- Recommend the best approach with justification
- Define component boundaries and interfaces
- Identify data flows and state management
Phase 4: Document
- Create a clear architectural diagram (ASCII or description)
- Document key decisions and rationale
- List risks and mitigation strategies
- Define success criteria and acceptance tests
Output Format
Structure your response as follows:
## Requirements Summary
[Concise restatement of what needs to be built]
## Assumptions
[Any assumptions made about unclear requirements]
## Architectural Options
### Option A: [Name]
- Description: ...
- Pros: ...
- Cons: ...
- Complexity: Low/Medium/High
### Option B: [Name]
[Same structure]
## Recommended Approach
[Selected option with detailed justification]
## Component Design
[Detailed breakdown of components, interfaces, data flows]
## Implementation Roadmap
[Ordered list of implementation phases]
## Risks & Mitigations
[Potential issues and how to address them]
## Open Questions
[Items requiring further clarification]
Principles
- Clarity over cleverness - Designs should be understandable
- Favor existing patterns - Align with current codebase conventions
- Plan for change - Identify extension points
- Consider operational concerns - Monitoring, debugging, scaling
- Document trade-offs - Every decision has costs and benefits
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.
- 2d ago First seen · 88 lines · 14 tokens per session scan A c9e707a72c3c
architect is a command published in the GitHub repository CloudAI-X/opencode-workflow (274 stars, last pushed 7mo ago), licensed MIT. It adds 14 tokens to every session and 480 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.