Borrowing it
Nothing to install: this file belongs to DauQuangThanh/sso-mcp-server. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/DauQuangThanh/sso-mcp-server/main/.claude/commands/rainbow.architect.mdgit clone --depth 1 https://github.com/DauQuangThanh/sso-mcp-serverWrote 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/dauquangthanh/sso-mcp-server/rainbow.architect)<a href="https://agentmods.dev/commands/dauquangthanh/sso-mcp-server/rainbow.architect"><img src="https://agentmods.dev/badge/commands/dauquangthanh/sso-mcp-server/rainbow.architect/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/dauquangthanh/sso-mcp-server/rainbow.architect"><img src="https://agentmods.dev/badge/commands/dauquangthanh/sso-mcp-server/rainbow.architect.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.00016 | $0.02244 |
| Opus 5 | $0.00008 | $0.01122 |
| Sonnet 5 | $0.00003 | $0.00449 |
| Haiku 4.5 | $0.00002 | $0.00224 |
Grade A, and why
rainbow.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 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.
This is a copy
97% identical to architect — 22 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 272 lines — stays where its author put it; the contents beside it link to each section on GitHub.
User Input
$ARGUMENTS
You MUST consider the user input before proceeding (if not empty).
Outline
IMPORTANT: Automatically generate a 'docs:' prefixed git commit message (e.g., 'docs: add system architecture documentation') and commit upon completion.
-
Setup: Run
.rainbow/scripts/bash/setup-architect.sh --jsonfrom repo root and parse JSON for ARCH_DOC, DOCS_DIR, SPECS_DIR. For single quotes in args like "I'm Groot", use escape syntax: e.g 'I'''m Groot' (or double-quote if possible: "I'm Groot"). -
Load context: Read
memory/ground-rules.mdand all feature specifications fromspecs/*/spec.md. Load ARCH_DOC template (already copied to docs/). -
Execute architecture workflow: Follow the structure in ARCH_DOC template to:
- Fill Executive Summary with product overview
- Identify stakeholders and architectural drivers
- Document quality attribute requirements (performance, security, scalability, etc.)
- Create C4 Model diagrams (Context, Container, Component, Code views)
- Design deployment architecture
- Document architecture decisions (ADRs)
- Map quality strategies to requirements
- Identify risks and technical debt
-
Stop and report: Command ends after architecture document completion. Report ARCH_DOC path and generated artifacts.
Phases
Phase 0: Architecture Analysis & Stakeholder Identification
-
Analyze feature specifications:
- Read all
specs/*/spec.mdfiles - Extract common patterns and requirements
- Identify system boundaries
- List all external integrations
- Read all
-
Identify stakeholders from ground-rules and specs:
- End users and their concerns
- Development team requirements
- Operations team needs
- Security and compliance requirements
- Business stakeholders
-
Extract architectural drivers:
- Business goals from feature specs
- Quality attributes (performance, scalability, security, etc.)
- Technical constraints from ground-rules
- Organizational constraints
- Assumptions and dependencies
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 · 272 lines · 16 tokens per session scan A 3f503ebf73b9
rainbow.architect is a command published in the GitHub repository DauQuangThanh/sso-mcp-server (0 stars, last pushed 8mo ago), licensed MIT. It adds 16 tokens to every session and 2,244 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 97% identical to architect, differing in 22 lines, and is treated as a copy.
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.