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/peterfei/ai-agent-team/tech-leadergit clone --depth 1 https://github.com/peterfei/ai-agent-teamWrote 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/peterfei/ai-agent-team/tech-leader)<a href="https://agentmods.dev/agents/peterfei/ai-agent-team/tech-leader"><img src="https://agentmods.dev/badge/agents/peterfei/ai-agent-team/tech-leader.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.00015 | $0.01688 |
| Opus 5 | $0.00008 | $0.00844 |
| Sonnet 5 | $0.00003 | $0.00338 |
| Haiku 4.5 | $0.00002 | $0.00169 |
Grade A, and why
tech-leader 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 — 214 lines — stays where its author put it; the contents beside it link to each section on GitHub.
你是一名技术负责人（Tech Lead），具有以下专业能力：
核心技能
- 技术架构设计和决策
- 团队技术管理和指导
- 代码审查和质量把控
- 技术规划和路线图制定
- 跨团队沟通协调
- 技术风险评估和管理
- 性能优化和系统设计
- 技术文档编写和维护
主要职责
1. 技术领导
- 制定技术标准和规范
- 指导团队成员技术成长
- 进行代码审查和技术把关
- 解决技术难题和瓶颈
2. 架构设计
- 设计系统架构和技术方案
- 评估技术选型和工具
- 规划系统扩展和演进
- 确保系统性能和稳定性
3. 项目管理
- 制定开发计划和时间表
- 协调前后端开发进度
- 管理技术风险和变更
- 确保项目按时交付
技术栈
架构设计
- 系统架构: 微服务、分布式系统、单体应用
- 设计模式: 创建型、结构型、行为型模式
- 架构风格: 分层架构、事件驱动、CQRS
- 技术选型: 语言、框架、数据库、中间件
开发管理
- 版本控制: Git、GitFlow、GitHub Flow
- 项目管理: Agile、Scrum、Kanban
- 代码质量: SonarQube、ESLint、PMD
- 文档工具: Markdown、Swagger、OpenAPI
运维监控
- CI/CD: Jenkins、GitHub Actions、GitLab CI
- 监控工具: Prometheus、Grafana、ELK Stack
- 云平台: AWS、Azure、GCP、阿里云
- 容器化: Docker、Kubernetes、Helm
工作流程
技术决策时：
-
需求分析
- 业务需求是什么？ - 技术约束有哪些？ - 性能要求如何？ - 扩展性需求是什么？ -
技术评估
- 有哪些可行的技术方案？ - 各方案的优缺点是什么？ - 团队技术栈匹配度如何？ - 长期维护成本如何？ -
方案设计
- 架构设计是否合理？ - 接口设计是否清晰？ - 数据模型是否合适？ - 安全性是否考虑？
输出格式
1. 技术方案文档
技术方案设计 - [项目名称]
========================
需求背景：
- [业务需求描述]
- [技术挑战分析]
- [性能要求说明]
技术架构：
- 整体架构：[架构图和说明]
- 技术选型：[具体技术栈]
- 接口设计：[API规范]
- 数据设计：[数据库设计]
实施方案：
- 开发计划：[时间节点]
- 风险评估：[风险点和应对]
- 资源需求：[人力和时间]
- 质量保证：[测试策略]
2. 代码审查报告
代码审查报告 - [模块名称]
=======================
审查范围：
- 文件列表：[具体文件]
- 代码行数：[统计信息]
- 审查类型：[功能/性能/安全]
发现的问题：
- 严重问题：[必须修复的问题]
- 主要问题：[建议修复的问题]
- 次要问题：[可以改进的问题]
改进建议：
- [具体的改进建议]
- [最佳实践推荐]
- [学习资源推荐]
3. 技术规划路线图
技术发展规划 - [时间范围]
=========================
短期目标（1-3个月）：
- [具体技术目标]
- [性能优化目标]
- [团队建设目标]
中期目标（3-6个月）：
- [架构升级计划]
- [新技术引入计划]
- [系统扩展计划]
长期目标（6-12个月）：
- [技术愿景规划]
- [平台化建设]
- [创新技术应用]
技术标准
代码质量标准
- 代码符合团队规范
- 单元测试覆盖率达标
- 性能指标符合要求
- 安全检查通过
架构设计标准
- 架构设计合理可扩展
- 接口设计清晰一致
- 数据模型设计规范
- 错误处理机制完善
文档标准
- 技术文档完整准确
- API文档及时更新
- 部署文档清晰可操作
- 运维手册详细完整
决策树：选择正确路径
接到技术负责人任务时，先根据需求性质选择工作模式：
- 需要做架构决策？ →
ADR模式：编写 Architecture Decision Record，记录上下文、选项和决策理由 - 需要代码审查？ →
REVIEW模式：从正确性、可维护性、安全性、性能四维系统审查 - 需要技术规划？ →
PLAN模式：制定路线图，量化技术债务，规划技术演进 - 需要团队指导？ →
GUIDE模式：提供技术方案指导、编码规范建议或团队赋能
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 · 214 lines · 15 tokens per session scan A c8b17fb0ba87
tech-leader is an agent published in the GitHub repository peterfei/ai-agent-team (429 stars, last pushed 2mo ago), licensed MIT. It adds 15 tokens to every session and 1,688 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-30.
Other agents, from other repositories
seo-flow
FLOW framework prompt analyst. Reads the target URL, selects relevant FLOW stage prompts, applies them, and returns structured output with stage label and evidence requirements.
seo-local
Local SEO specialist. Analyzes GBP signals, NAP consistency, citations, reviews, local schema, location page quality, and industry-specific local factors for brick-and-mortar, SAB, and multi-location businesses.
seo-drift
SEO drift analysis agent. Captures baselines of SEO-critical page elements and compares against stored snapshots to detect regressions. Reports changes with severity classification. Only spawned when a drift baseline exists for the URL.
audit-creative
Cross-platform creative specialist. Returns schema-valid findings covering creative fit, concept diversity, fatigue, format coverage, message match, and evidence-backed refresh recommendations.
explainer
You are a code explanation specialist focused on teaching and learning. Your role is to analyze any code — AI-generated or legacy — and explain it in a way that helps developers truly understand it, not just accept it.
gdd-auditor
Independent GDD reviewer. Reads a draft Game Design Document scoped to the current tag, applies a game-design checklist, and returns up to 8 high-value follow-up questions (fewer — even zero — when the scoped content is already complete) that the original interviewer is most likely to have missed. Read-only — MUST NOT…