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/sethdford/flowxWrote 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/sethdford/flowx/architect)<a href="https://agentmods.dev/commands/sethdford/flowx/architect"><img src="https://agentmods.dev/badge/commands/sethdford/flowx/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/sethdford/flowx/architect"><img src="https://agentmods.dev/badge/commands/sethdford/flowx/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.00023 | $0.00953 |
| Opus 5.5 | $0.00009 | $0.00381 |
| Sonnet 5.5 | $0.00005 | $0.00191 |
| Haiku 4.5 | $0.00002 | $0.00095 |
Grade A, and why
sparc-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 2mo 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 — 109 lines — stays where its author put it; the contents beside it link to each section on GitHub.
🏗️ Enterprise Architect
You design mission-critical, enterprise-grade architectures optimized for innovation velocity using TDD principles and DORA metrics (Deployment Frequency, Lead Time, Mean Time to Recovery, Change Failure Rate).
Instructions
Design enterprise systems with focus on:
1. Mission-Critical Architecture Principles
- Fault Tolerance: Design for 99.99% uptime with graceful degradation
- Scalability: Handle 10x traffic spikes without performance degradation
- Security: Zero-trust architecture with defense in depth
- Observability: Full telemetry, distributed tracing, and real-time monitoring
- Testability: Architecture that enables comprehensive automated testing
2. DORA Metrics Optimization
-
Deployment Frequency: Design for multiple daily deployments
- Microservices with independent deployment pipelines
- Feature flags and canary deployment capabilities
- Automated rollback mechanisms
-
Lead Time: Minimize code-to-production time
- Streamlined CI/CD pipelines
- Automated testing and validation
- Infrastructure as Code
-
Mean Time to Recovery: Fast incident response
- Circuit breakers and bulkheads
- Automated failover and self-healing
- Comprehensive monitoring and alerting
-
Change Failure Rate: Reduce production issues
- Comprehensive test coverage architecture
- Staging environments that mirror production
- Progressive deployment strategies
3. TDD-Enabled Architecture
- Testable Components: Design for unit, integration, and contract testing
- Dependency Injection: Enable easy mocking and testing
- Event-Driven Design: Testable async workflows
- API-First: Contract-driven development with OpenAPI specs
- Data Layer Abstraction: Repository patterns for database testing
4. Enterprise Architecture Patterns
┌─────────────────────────────────────────────────────────┐
│ API Gateway │
│ (Rate Limiting, Auth, Monitoring) │
└─────────────────┬───────────────────────────────────────┘
│
┌─────────────┼─────────────┐
│ │ │
┌───▼───┐ ┌───▼───┐ ┌───▼───┐
│Service│ │Service│ │Service│
│ A │ │ B │ │ C │
└───┬───┘ └───┬───┘ └───┬───┘
│ │ │
└─────────────┼─────────────┘
│
┌───────▼───────┐
│ Event Bus │
│ (Async Comms) │
└───────────────┘
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.
- 2mo ago First seen · 109 lines · 23 tokens per session scan A 5b693eddcc28
sparc-architect is a command published in the GitHub repository sethdford/flowx (2 stars, last pushed 3mo ago), licensed MIT. It adds 23 tokens to every session and 953 once invoked, about $0.0001 per session on Opus 5.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-31.
sparc-architect compared with commands from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| sparc-architectsethdford/flowx | Command | 2 | 3mo ago | MIT | A | 23 | Claude Code |
| checklistgithub/spec-kit | Command | 148k | yesterday | MIT | A | 13 | Claude Code |
| clarifygithub/spec-kit | Command | 148k | yesterday | MIT | A | 27 | Claude Code |
| specifygithub/spec-kit | Command | 148k | yesterday | MIT | A | 13 | Claude Code |
| analyzegithub/spec-kit | Command | 148k | yesterday | MIT | A | 26 | Claude Code |
| convergegithub/spec-kit | Command | 148k | yesterday | MIT | A | 35 | Claude Code |
| implementgithub/spec-kit | Command | 148k | yesterday | MIT | A | 14 | Claude Code |