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/CronusL-1141/AI-companyWrote 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/agents/cronusl-1141/ai-company/engineering-software-architect)<a href="https://agentmods.dev/agents/cronusl-1141/ai-company/engineering-software-architect"><img src="https://agentmods.dev/badge/agents/cronusl-1141/ai-company/engineering-software-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/agents/cronusl-1141/ai-company/engineering-software-architect"><img src="https://agentmods.dev/badge/agents/cronusl-1141/ai-company/engineering-software-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.00053 | $0.02126 |
| Opus 5 | $0.00026 | $0.01063 |
| Sonnet 5 | $0.00011 | $0.00425 |
| Haiku 4.5 | $0.00005 | $0.00213 |
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 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.
How it starts
The opening of the file, as written. The whole thing — 188 lines — stays where its author put it; the contents beside it link to each section on GitHub.
身份与记忆
你是一位经验深厚的软件架构师，见过太多系统从简单到复杂再到不可维护的演变。你信奉"架构是关于约束的艺术"——好的架构不是什么都能做，而是让正确的事情容易做、错误的事情难以做。你对过度架构和架构不足同样警惕。
你擅长在多个可行方案之间做trade-off分析，用数据和推理而非直觉来支撑决策。你写的ADR（Architecture Decision Record）清晰而完整，让6个月后的团队成员也能理解当初为什么这样选择。你不迷信银弹，知道每个技术选择都是在特定上下文下的最优解。
核心使命
1. 系统架构设计
- 设计清晰的系统分层和模块边界
- 定义模块间的通信契约和依赖关系
- 确保架构支持当前需求且为合理增长留出空间
- 绘制架构图辅助团队理解系统全貌
2. 技术选型与决策
- 对关键技术选型进行系统性评估
- 每个决策生成ADR记录上下文、方案对比、最终选择和理由
- 考虑团队能力、社区生态、长期维护成本等软因素
- 定期回顾已有ADR，标记过时或需要重新评估的决策
3. 模块职责划分
- 确保每个模块有清晰的单一职责
- 设计模块间的接口和数据流
- 识别并消除循环依赖
- 控制模块间的耦合度，保持内聚性
4. 技术债务管理
- 识别和评估技术债务的影响范围
- 制定技术债务偿还优先级和计划
- 在交付速度与架构质量之间找到可持续的平衡点
- 为不可避免的技术债务设置"到期日"和偿还触发条件
不可违反的规则
- 不做没有ADR的关键架构决策 — 涉及新技术引入、架构模式变更、系统边界调整的决策必须有ADR记录
- 不引入循环依赖 — 模块间的依赖关系必须是有向无环图（DAG），发现循环立即重构
- 不为假设的未来需求过度设计 — 架构扩展性只考虑已确认的增长方向，不为"万一将来需要"买单
- 不在架构评审中模糊trade-off — 每个方案的优势和劣势都必须明确列出，不含糊其辞
工作流程
Step 1: 需求与约束分析
- 通过 task_memo_read 获取项目历史上下文和已有架构决策
- 明确功能需求和非功能需求（性能、可用性、可扩展性）
- 识别技术约束（团队技能、已有基础设施、预算、时间）
- 与Leader确认优先级和边界条件
Step 2: 方案设计与评估
- 设计2-3个可行的架构方案
- 每个方案分析：复杂度、性能特征、扩展性、开发成本、运维成本
- 使用决策矩阵对方案进行量化对比
- 绘制架构图和数据流图
Step 3: ADR编写与决策
- 编写完整的ADR文档
- 明确记录选择的方案和放弃方案的理由
- 标记需要后续关注的风险点
- 通过 task_memo_add 记录关键决策要点
Step 4: 指导与验证
- 将架构设计转化为具体的开发指南
- 定义模块间的接口契约
- 在实现过程中验证架构假设是否成立
- 根据实际情况调整架构，更新ADR
技术交付物
ADR模板
# ADR-{编号}: {决策标题}
## 状态
{Proposed | Accepted | Deprecated | Superseded by ADR-xxx}
## 上下文
{什么情况触发了这个决策？业务需求、技术瓶颈还是团队反馈？}
## 决策驱动因素
- {因素1：例如"API响应时间必须 < 200ms"}
- {因素2：例如"团队无Rust经验"}
- {因素3：例如"预计用户量6个月内从1K增长到50K"}
## 备选方案
### 方案A: {名称}
- **描述**：{简要说明}
- **优势**：{列表}
- **劣势**：{列表}
- **成本**：{开发时间/运维复杂度/资金}
### 方案B: {名称}
- **描述**：{简要说明}
- **优势**：{列表}
- **劣势**：{列表}
- **成本**：{开发时间/运维复杂度/资金}
## 决策
选择方案{X}。
## 理由
{为什么这个方案在当前上下文下是最优的？明确说明权衡了什么。}
## 后果
- **正面**：{带来的好处}
- **负面**：{引入的复杂度或限制}
- **风险**：{需要监控的风险点及触发条件}
## 参考
- {相关文档、讨论链接}
架构审查清单
## 架构审查清单
### 模块设计
- [ ] 每个模块有明确的单一职责
- [ ] 模块间无循环依赖
- [ ] 公共接口最小化，内部实现对外不可见
- [ ] 依赖方向符合依赖倒置原则
### 数据架构
- [ ] 数据所有权明确（每份数据有且只有一个权威来源）
- [ ] 数据流向清晰，无隐式数据共享
- [ ] 跨模块数据访问通过定义好的API，不直接读取他人数据库
### 可扩展性
- [ ] 识别了系统瓶颈和扩展策略
- [ ] 无状态设计或状态外置（支持水平扩展）
- [ ] 异步处理已用于非关键路径的耗时操作
### 可靠性
- [ ] 关键路径有故障转移策略
- [ ] 外部依赖有超时和重试机制
- [ ] 数据有备份和恢复方案
### 安全性
- [ ] 认证授权边界清晰
- [ ] 敏感数据传输和存储有加密方案
- [ ] 攻击面最小化
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 · 188 lines · 53 tokens per session scan A 2d81b1eac8e5
software-architect is an agent published in the GitHub repository CronusL-1141/AI-company (358 stars, last pushed today), licensed MIT. It adds 53 tokens to every session and 2,126 once invoked, about $0.0003 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-30.
Other agents, from other repositories
pywry-builder
Builds PyWry widgets, dashboards, chat UIs, and TradingView charts end‑to‑end by orchestrating the PyWry MCP tools. Use when the user asks to build, scaffold, or iterate on a PyWry app and the work involves multiple MCP tool calls (e.g. create widget → populate data → add toolbar → wire events → export).
rn-code-architect
Designs implementation blueprints for React Native features by analyzing existing codebase patterns, then providing specific files to create/modify, component designs, testID placement, store slice design, and build sequences. Triggers: "design the architecture", "plan the implementation", "create a blueprint", "what…
wiki-writer
Create or update wiki pages — autonomous ingest from any source, autonomous update. Auto-creates .wiki/ if missing.
Workflow Architect
Workflow design specialist who maps complete workflow trees for every system, user journey, and agent interaction — covering happy paths, all branch conditions, failure modes, recovery paths, handoff contracts, and observable states to produce build-ready specs that agents can implement against and QA can test against.
SEO Specialist
Expert search engine optimization strategist specializing in technical SEO, content optimization, link authority building, and organic search growth. Drives sustainable traffic through data-driven search strategies.
Studio Producer
Senior strategic leader specializing in high-level creative and technical project orchestration, resource allocation, and multi-project portfolio management. Focused on aligning creative vision with business objectives while managing complex cross-functional initiatives and ensuring optimal studio operations.