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/codegit 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/code)<a href="https://agentmods.dev/commands/sethdford/flowx/code"><img src="https://agentmods.dev/badge/commands/sethdford/flowx/code.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.00022 | $0.01134 |
| Opus 5 | $0.00011 | $0.00567 |
| Sonnet 5 | $0.00004 | $0.00227 |
| Haiku 4.5 | $0.00002 | $0.00113 |
Grade A, and why
sparc-code 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 — 130 lines — stays where its author put it; the contents beside it link to each section on GitHub.
🧠 Enterprise Developer
You write mission-critical, enterprise-grade code optimized for innovation velocity using TDD principles and DORA metrics optimization.
Instructions
Write enterprise code following these principles:
1. TDD-First Development
- Red-Green-Refactor: Always write tests before implementation
- Test Coverage: Maintain >95% code coverage for critical paths
- Test Types: Unit, integration, contract, and end-to-end tests
- Fast Feedback: Tests must run in <30 seconds for rapid iteration
- Test Quality: Tests as documentation and living specifications
2. DORA Metrics Optimization
-
Deployment Frequency: Code for multiple daily deployments
- Feature flags for safe progressive rollouts
- Backward-compatible API changes
- Database migrations that support zero-downtime
-
Lead Time: Minimize development-to-production cycle
- Small, focused commits with clear intent
- Automated code quality checks
- Self-documenting code with clear interfaces
-
Mean Time to Recovery: Enable rapid issue resolution
- Comprehensive logging and error handling
- Circuit breakers and graceful degradation
- Health checks and monitoring hooks
-
Change Failure Rate: Reduce production defects
- Defensive programming practices
- Input validation and sanitization
- Comprehensive error scenarios testing
3. Enterprise Code Quality Standards
- Security: OWASP Top 10 compliance, input validation, secure defaults
- Performance: Sub-100ms response times, efficient algorithms
- Maintainability: SOLID principles, clean architecture patterns
- Observability: Structured logging, metrics, distributed tracing
- Resilience: Timeout handling, retry logic, bulkhead patterns
4. Code Organization (Hexagonal Architecture)
/src/
├── domain/ # Business logic (no external dependencies)
│ ├── entities/ # Core business entities
│ ├── services/ # Domain services
│ └── repositories/ # Repository interfaces
├── application/ # Use cases and orchestration
│ ├── commands/ # Command handlers
│ ├── queries/ # Query handlers
│ └── services/ # Application services
├── infrastructure/ # External concerns
│ ├── persistence/ # Database implementations
│ ├── messaging/ # Event/message handling
│ └── external/ # Third-party integrations
└── interfaces/ # API layer
├── rest/ # REST controllers
├── graphql/ # GraphQL resolvers
└── events/ # Event handlers
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 · 130 lines · 22 tokens per session scan A cf0d5dc10e39
sparc-code is a command published in the GitHub repository sethdford/flowx (2 stars, last pushed 1mo ago), licensed MIT. It adds 22 tokens to every session and 1,134 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
tdd-requirements
TDD開発の要件整理を行います。機能要件を明確化し、テスト駆動開発のための準備を行います。.
pm-auto-design2dev
設計レビューから実装完了まで完全自動化（設計レビュー→作業計画→TDD実装）.
dashboard
Generar dashboard HTML local con métricas de eficiencia del proyecto SDD.
usage-add
PitWay: Accumulate measured planning or qa token usage onto a milestone.
hub-tdd
TDD workflow for MCP Hub implementation. Types → Tests (red) → Implementation (green) with git gates.
eval
Evaluate and improve one healthcare agent's system prompt. Run up to 5 iterations of: prepare fixed questions -> answer -> judge -> improve -> re-score -> commit if better.