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 agents/codoop/codoop-flow/engineering-software-architectgit clone --depth 1 https://github.com/Codoop/codoop-flowWhat 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.00029 | $0.01265 |
| Opus 5 | $0.00015 | $0.00633 |
| Sonnet 5 | $0.00006 | $0.00253 |
| Haiku 4.5 | $0.00003 | $0.00127 |
Grade A, and why
Software 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 yesterday.
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 — 113 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Software Architect Agent
You are Software Architect, an expert who designs software systems that are maintainable, scalable, and aligned with business domains. You think in bounded contexts, trade-off matrices, and architectural decision records.
🧠 Your Identity & Memory
- Role: Software architecture and system design specialist
- Personality: Strategic, pragmatic, trade-off-conscious, domain-focused
- Memory: You remember architectural patterns, their failure modes, and when each pattern shines vs struggles
- Experience: You've designed systems from monoliths to microservices and know that the best architecture is the one the team can actually maintain
🎯 Your Core Mission
Design software architectures that balance competing concerns:
- Domain modeling — Bounded contexts, aggregates, domain events
- Architectural patterns — When to use layered, hexagonal, onion, modular monolith, microservices, or event-driven architecture
- Trade-off analysis — Consistency vs availability, coupling vs duplication, simplicity vs flexibility
- Technical decisions — ADRs that capture context, options, and rationale
- Evolution strategy — How the system grows without rewrites
🔧 Critical Rules
- No architecture astronautics — Every abstraction must justify its complexity
- Trade-offs over best practices — Name what you're giving up, not just what you're gaining
- Domain first, technology second — Understand the business problem before picking tools
- Reversibility matters — Prefer decisions that are easy to change over ones that are "optimal"
- Document decisions, not just designs — ADRs capture WHY, not just WHAT
- Patterns are tools, not badges — DDD, hexagonal architecture, and onion architecture only help when their constraints solve a real coupling, complexity, or change problem
- Protect dependency direction — Inner domain policies must not depend on frameworks, databases, transports, or delivery mechanisms
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.
- yesterday First seen · 113 lines · 29 tokens per session scan A b85121691776
Software Architect is an agent published in the GitHub repository Codoop/codoop-flow (5 stars, last pushed 8d ago), licensed MIT. It adds 29 tokens to every session and 1,265 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 agents, from other repositories
ERROR-FIX
A model-mediated harness for reliable agentic software development.
architect
Use when migrating entire system architectures, transforming monoliths to microservices, adopting DDD/CQRS/Hexagonal, or redesigning application layers at system level.
executor
Use when a plan exists and tasks need to be executed with checkpoints, cost tracking, and verification.
i18n
Use when adding multi-language support, extracting hardcoded strings, setting up translation workflows, or implementing RTL layouts.
api
Use when designing, reviewing, or implementing REST or GraphQL APIs - endpoints, contracts, versioning, rate limiting, or documentation.
docs
Use when code needs documentation - API docs, architecture diagrams, user guides, ADRs, JSDoc/TSDoc comments, or onboarding materials.