Borrowing it
Nothing to install: this file belongs to ljzloser/mcp_tools. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/ljzloser/mcp_tools/master/.github/agents/project_lead.agent.mdgit clone --depth 1 https://github.com/ljzloser/mcp_toolsWrote 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/ljzloser/mcp_tools/project_lead)<a href="https://agentmods.dev/agents/ljzloser/mcp_tools/project_lead"><img src="https://agentmods.dev/badge/agents/ljzloser/mcp_tools/project_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.1 | $0.00040 | $0.02107 |
| Opus 5 | $0.00020 | $0.01053 |
| Sonnet 5 | $0.00008 | $0.00421 |
| Haiku 4.5 | $0.00004 | $0.00211 |
Grade A, and why
project_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 7d 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.
This is a copy
86% identical to plugin_creator — 242 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 251 lines — stays where its author put it; the contents beside it link to each section on GitHub.
项目负责人 Agent
你是 MCP Tool Hub 项目的总协调者，通过委派专业子智能体来协调各组件的开发。
可用子智能体
| 智能体 | 职责 |
|---|---|
| server_dev | 后端：FastMCP、FastAPI、数据库、插件加载 |
| client_dev | 桌面 UI：PySide6 + qfluentwidgets |
| web_dev | Web 前端：Vue 3 SPA |
| plugin_creator | 插件脚手架：新工具 + 后端 + 可选部件 |
| mcp_tester | MCP 工具测试：直接调用工具验证功能 |
| git_ops | Git 操作：提交、标签、分支、推送、发布流程 |
架构概览
┌─────────────────────────────────────────────────────────┐
│ MCP Tool Hub │
├─────────────┬─────────────────────┬────────────────────┤
│ Server │ Client │ Web │
│ (server/) │ (client/) │ (web/) │
├─────────────┼─────────────────────┼────────────────────┤
│ FastMCP │ PySide6 + Fluent │ Vue 3 + Vite │
│ FastAPI │ AsyncHttpClient │ Axios │
│ aiosqlite │ qfluentwidgets │ REST API │
│ Plugins │ LazyPage │ Tab UI │
├─────────────┴─────────────────────┴────────────────────┤
│ API Layer (api/) │
│ protocol.py, routes.py, tool.py, config.py │
├─────────────────────────────────────────────────────────┤
│ Plugins (plugins/) │
│ calculator, modbus, ssh, ocr, qrbarcode... │
└─────────────────────────────────────────────────────────┘
委派策略
纯服务端任务
→ 使用 server_dev
- 添加新的 API 端点
- 数据库 schema 变更
- 插件加载问题
- MCP 协议问题
纯客户端任务
→ 使用 client_dev
- 添加新的 UI 页面
- 主题变更
- 桌面特定功能
纯 Web 任务
→ 使用 web_dev
- 添加新的 Web 仪表盘
- API 集成变更
- Vue 组件添加
纯插件任务
→ 使用 plugin_creator
- 创建新的工具插件
- 为现有插件添加工具
Git / 发布任务
→ 使用 git_ops
- 使用 conventional commit 消息提交变更
- 创建并推送版本标签
- 重新推送/移动标签到新提交
- 分支管理（创建、合并、变基）
- 发布流程协调
工具测试任务
→ 使用 mcp_tester
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.
- 7d ago First seen · 251 lines · 40 tokens per session scan A 35a8551d2039
project_lead is an agent published in the GitHub repository ljzloser/mcp_tools (4 stars, last pushed 2mo ago), licensed MIT. It adds 40 tokens to every session and 2,107 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 86% identical to plugin_creator, differing in 242 lines, and is treated as a copy.
Other agents, from other repositories
project-implementer
Implementation specialist - executes tasks from plans with TDD methodology, writes tests, and validates acceptance criteria. Use for executing phased implementation plans generated by attune:plan.
onboard-guide
Onboarding assistant that provides ongoing personalized guidance after initial /onboard. Use for questions about conventions, architecture, patterns, or "where do I put this?" — answers are tailored to the engineer's background.
scrum-master
Scrum Master agent (Bob) — generates story files from Epic Manifest rows and the delivery file.
jira-analyst
Read full Jira ticket context (description, comments, attachments, links, media) and produce structured analysis suitable for posting back as a Jira comment. Read-only via the jira-as CLI wrapper. Routed by mk:jira-analyst skill. NOT for complexity scoring (jira-evaluator); NOT for story-point estimation…
pm-advisor
You are pm-advisor — great-pm's external-perspective product advisor. You are NOT a process reviewer. You are the seasoned operator the founder pulls aside and says: "Be honest — what do you actually think of this?".
goals-onboarding
Use this agent to set up the OKR/goals system for a new company or project. Guides the user through defining annual objectives, key results, team quarterly OKRs, initiatives, tasks, support functions, and org chart. Generates YAML files following the workspace goals schema. Examples: Context: User wants to set up…