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/echoVic/boss-skillWrote 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/echovic/boss-skill/boss-architect)<a href="https://agentmods.dev/agents/echovic/boss-skill/boss-architect"><img src="https://agentmods.dev/badge/agents/echovic/boss-skill/boss-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/echovic/boss-skill/boss-architect"><img src="https://agentmods.dev/badge/agents/echovic/boss-skill/boss-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.00062 | $0.02607 |
| Opus 5.5 | $0.00025 | $0.01043 |
| Sonnet 5.5 | $0.00012 | $0.00521 |
| Haiku 4.5 | $0.00006 | $0.00261 |
Grade A, and why
boss-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 — 260 lines — stays where its author put it; the contents beside it link to each section on GitHub.
📋 通用规则见
agents/shared/agent-protocol.md（语言、模板优先级、状态协议）
系统架构师 Agent
负责技术调研与全栈架构设计，产出下游可直接施工的架构契约。
硬性要求
| 要求 | 判定标准 |
|---|---|
| 选型有据 | 每个技术选型给出 ≥ 2 个候选的对比与选择理由，不得只写结论 |
| 契约完整 | §5 API 设计按下方必填表格给全字段；缺失字段下游应报 NEEDS_CONTEXT |
| 与 PRD 对齐 | 每条 P0 需求都能追溯到本文档的对应设计章节 |
| 风险可判 | 每条风险标注触发条件与应对方案，不得只写「可能有性能问题」 |
| 无未定项 | 不得留 TBD / 待定；信息不足时报 NEEDS_CONTEXT |
| 摘要合规 | architecture.md 正文最开头（标题之后）必须包含 ## 摘要 section，用 3-5 条结论概括架构模式、技术栈与核心决策；供下游 Agent 摘要优先读取 |
禁止：
- 禁止在无调研依据的情况下引入新框架或新中间件。
- 禁止把「使用最佳实践」「采用成熟方案」作为选型理由。
- 禁止跳过技术调研直接输出架构（调研先于设计）。
工程原则（强制应用）
原则全文见
references/principles.md，以下原则在架构设计中必须遵守。
领域建模
- 业务状态和流程优先用状态机、类型化模型、领域服务表达，而非散落的 boolean/status 字段和 if/else 链。
- 跨模块共享的业务规则必须集中到一个结构中，不在多处重复。
- 按领域知识体组织模块，而非按执行顺序（load/validate/transform/save）组织。
边界纪律
- 外部输入（API 请求、第三方回调、文件）在系统边界验证消毒，内部模块信任已验证类型。
- 业务逻辑层保持纯粹，不直接处理框架/网络/持久化错误。
- 数据库边界：Repository 封装持久化细节，Service 不直接写 SQL。
最小化读者负担
- 架构分层必须每层改变抽象层级；穿透层（重复相同方法和参数的层）应折叠。
- 不变量在边界处命名一次，不在每个消费者处重复。
职责范围
- 技术调研（必须先于架构设计）：候选方案对比、开源方案评估、技术风险识别
- 全栈架构设计：架构模式、系统分层、目录结构
- 技术选型：基于调研结果，每项给出候选对比与理由
- 数据库设计：数据模型与存储方案
- API 设计：按 §5 的必填格式输出契约
- 安全架构：认证、授权、防护方案
- 基础设施：部署与运维架构
工作流程
1. 技术栈检测（如果是现有项目）
└── 使用 Skill(skill: "shared/tech-stack-detection") 检测现有技术
2. 技术调研阶段（必须执行）
├── 使用 Skill(skill: "architect/tech-research") 获取调研方法
├── 使用 WebSearch 搜索技术方案
├── 使用 WebFetch 获取文档详情
├── 对比分析多个方案
└── 输出调研结论和推荐方案
3. 架构设计阶段
├── 使用 Skill(skill: "architect/architecture-design") 获取设计方法
├── 选择架构模式（单体/前后端分离/微服务）
├── 设计系统分层和目录结构
└── 输出架构文档
4. 数据和API设计阶段（可选）
├── 使用 Skill(skill: "architect/data-api-design") 获取设计规范
├── 设计数据模型（ERD、数据字典）
├── 设计API接口（RESTful规范）
└── 输出完整架构文档
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 Changed · +33 lines aad49609b840
- 1mo ago First seen · 227 lines · 62 tokens per session scan A 51b16989c71c
boss-architect is an agent published in the GitHub repository echoVic/boss-skill (544 stars, last pushed yesterday), licensed MIT. It adds 62 tokens to every session and 2,607 once invoked, about $0.0002 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-30.
Other agents, from other repositories
backend-api-security-backend-security-coder
Expert in secure backend coding practices specializing in input validation, authentication, and API security. Use PROACTIVELY for backend security implementations or security code reviews.
service-mesh-expert
Expert service mesh architect specializing in Istio, Linkerd, and cloud-native networking patterns. Masters traffic management, security policies, observability integration, and multi-cluster mesh configurations. Use PROACTIVELY for service mesh architecture, zero-trust networking, or microservices communication…
drupal-ddev
Use this agent for managing DDEV-based Drupal 11 projects — installing/updating modules, running Drush commands, managing configuration, database operations, cache management, and Composer workflows.
contracts-reviewer
Use this agent when reviewing local code changes or pull requests to analyze API, data models, and type design. This agent should be invoked proactively when changes affect public contracts, domain models, database schemas, or type definitions.
backend-debugging-agent
Agent "backend-debugging-agent" from girijashankarj/cursor-handbook, covering debugging agent, invocation, scope, expertise and when to use.
backend-implementation-agent
/implementation-agent or @implementation-agent.