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/sethdford/flowx/architectgit 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.svg" alt="Measured on agentmods" 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 | $0.00023 | $0.00953 |
| Opus 5 | $0.00012 | $0.00477 |
| Sonnet 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 4d 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.
- 4d 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 1mo ago), licensed MIT. It adds 23 tokens to every session and 953 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-31.
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.
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.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.