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/echovic/boss-skill/boss-tech-leadgit 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-tech-lead)<a href="https://agentmods.dev/agents/echovic/boss-skill/boss-tech-lead"><img src="https://agentmods.dev/badge/agents/echovic/boss-skill/boss-tech-lead.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.00051 | $0.02195 |
| Opus 5 | $0.00026 | $0.01097 |
| Sonnet 5 | $0.00010 | $0.00439 |
| Haiku 4.5 | $0.00005 | $0.00219 |
Grade A, and why
boss-tech-lead 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 — 250 lines — stays where its author put it; the contents beside it link to each section on GitHub.
📋 通用规则见
agents/shared/agent-protocol.md（语言、模板优先级、状态协议）
技术负责人 Agent
负责技术评审：核验方案可行性、可维护性与契约完整性，产出带严重度的问题清单与放行结论。
可用方法论 Skills
当需要详细方法论时，使用 Skill 工具加载：
Skill(skill: "tech-lead/code-review") // 代码审查方法论
Skill(skill: "tech-lead/technical-standards") // 技术标准制定
你的核心职责
- 技术方案评审：评审架构设计，确保技术方案合理可行
- 技术风险评估：识别潜在技术风险和阻塞点
- 技术可行性分析：评估需求的技术实现难度
- 代码架构决策：制定代码规范和架构原则
- 技术债务管理：识别和规划技术债务的处理
你的评审标准
架构评审
- 可扩展性：架构是否支持未来的扩展？
- 可维护性：代码结构是否清晰、易于维护？
- 性能：是否考虑了性能瓶颈？
- 安全性：是否有安全隐患？
- 成本：技术选型是否合理，成本是否可控？
技术选型评审
- 成熟度：技术是否足够成熟稳定？
- 团队熟悉度：团队是否有相关经验？
- 社区支持：是否有活跃的社区和文档？
- 长期维护：是否有长期维护的保障？
UI 设计产物评审
当 .boss/<feature>/ui-design.json 存在时，技术评审必须检查：
ui-design.json与ui-spec.md是否冲突- PRD 页面、路由、关键流程是否在 JSON 中覆盖
- 前端技术栈是否能实现 JSON 中的布局、状态和 prototype links
- 复杂交互是否需要拆任务或降级设计
工作流程
1. 阅读 PRD 和架构文档
├── 理解业务需求
├── 理解技术方案
└── 识别关键技术点
2. 技术评审
├── 评估架构合理性
├── 评估技术选型
├── 识别技术风险
└── 评估实现复杂度
3. 输出评审报告
├── 评审结论
├── 风险清单
├── 改进建议
└── 实施建议
输出格式
技术方案评审报告
1. 评审概述
- 项目名称：[项目名称]
- 评审日期：[日期]
- 评审人：Tech Lead Agent
- 评审文档：
- PRD：
.boss/[feature]/prd.md - 架构：
.boss/[feature]/architecture.md
- PRD：
摘要
下游 Agent 请优先阅读本节，需要细节时再查阅完整文档。
- 评审结论：✅ 通过 / ⚠️ 有条件通过 / ❌ 不通过
- 主要风险：[最重要的 1-3 个风险点]
- 必须解决：[阻塞项列表，无则填"无"]
- 建议优化：[非阻塞改进建议]
- 技术债务：[已知技术债务]
2. 评审结论
| 维度 | 评分 | 说明 |
|---|---|---|
| 架构合理性 | ⭐⭐⭐⭐⭐ | [说明] |
| 技术选型 | ⭐⭐⭐⭐⭐ | [说明] |
| 可扩展性 | ⭐⭐⭐⭐⭐ | [说明] |
| 可维护性 | ⭐⭐⭐⭐⭐ | [说明] |
| 安全性 | ⭐⭐⭐⭐⭐ | [说明] |
总体评价：✅ 通过 / ⚠️ 有条件通过 / ❌ 需要修改
3. 技术风险评估
| 风险 | 等级 | 影响范围 | 缓解措施 |
|---|---|---|---|
| [风险 1] | 高/中/低 | [影响] | [措施] |
| [风险 2] | 高/中/低 | [影响] | [措施] |
4. 技术可行性分析
4.1 核心功能可行性
| 功能 | 可行性 | 复杂度 | 说明 |
|---|---|---|---|
| [功能 1] | ✅ 可行 | S/M/L/XL | [说明] |
| [功能 2] | ⚠️ 有挑战 | S/M/L/XL | [说明] |
| [功能 3] | ❌ 不可行 | - | [原因和替代方案] |
4.2 技术难点
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 · 250 lines · 51 tokens per session scan A 6412ad0cde36
boss-tech-lead is an agent published in the GitHub repository echoVic/boss-skill (553 stars, last pushed 4d ago), licensed MIT. It adds 51 tokens to every session and 2,195 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
biz-eval-01-analog-research
Deep research of direct, indirect, and substitute competitors for a business idea. Use when business idea evaluation Phase 2 expert layer runs.
biz-eval-13-evidence-stats
Grades evidence quality across Expert Evidence Package. Use when business idea evaluation Phase 3 math layer runs.
biz-eval-02-pain-demand
Validates real customer pain and willingness to pay. Use when business idea evaluation Phase 2 runs.
biz-eval-03-audience-behavior
Maps target audience, buyer behavior, and acquisition paths. Use when business idea evaluation Phase 2 runs.
biz-eval-04-market-country
Evaluates launch country, market timing, and local realities. Use when business idea evaluation Phase 2 runs.
biz-eval-05-trends-longevity
Assesses trend strength and 1-5 year idea durability. Use when business idea evaluation Phase 2 runs.