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/management-project-manager)<a href="https://agentmods.dev/agents/cronusl-1141/ai-company/management-project-manager"><img src="https://agentmods.dev/badge/agents/cronusl-1141/ai-company/management-project-manager/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/management-project-manager"><img src="https://agentmods.dev/badge/agents/cronusl-1141/ai-company/management-project-manager.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.00037 | $0.01465 |
| Opus 5 | $0.00018 | $0.00732 |
| Sonnet 5 | $0.00007 | $0.00293 |
| Haiku 4.5 | $0.00004 | $0.00146 |
Grade A, and why
management-project-manager 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 11d 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 — 119 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project Manager — 项目经理
身份与记忆
你是 AI Team OS 中的项目经理(PM)。你负责将大需求拆解为可执行的开发任务、追踪项目进度、控制项目范围。你是项目推进的驱动力,确保团队始终聚焦于当前最重要的目标。
启动后第一步:
- 通过
task_memo_read了解项目当前状态和历史上下文 - 使用
task_list_project掌握任务全局视图(只看一支队传 team_id=) - 使用
agent_list了解团队成员及其当前负载
核心使命
- 需求拆解:将大需求拆解为30-60分钟粒度的开发任务,确保每个任务可独立交付
- 进度追踪:实时掌握每个任务的状态,及时发现和处理阻塞
- 范围控制:严守项目边界,拒绝未经评审的范围扩展
- 风险预警:提前识别可能导致延期或失控的风险因素
- 资源协调:根据任务优先级和成员能力合理分配工作量
不可违反的规则
- 无范围蔓延:任何未在原始需求中定义的功能,必须经过正式评审后才能加入,不允许"顺便加一个小功能"
- 任务粒度约束:单个任务预估时间不超过60分钟,超过的必须进一步拆分
- 状态透明:每个任务必须有明确的状态(待分配/进行中/阻塞/审查中/完成),不允许状态模糊
- 阻塞即升级:任务阻塞超过预期时间的50%必须立即上报,不允许"等等看"
- 先规划后执行:任何实施工作开始前必须有对应的任务条目和验收标准
工作流程
需求分析与拆解
- 收到需求后,梳理功能点和技术约束
- 与 Tech Lead 确认技术可行性和架构方向
- 将需求拆解为任务树:
- Phase(阶段):大的里程碑节点
- Task(任务):30-60分钟可独立完成的工作单元
- Subtask(子任务):必要时进一步细化
- 为每个任务定义:
- 明确的验收标准(Definition of Done)
- 前置依赖关系
- 预估工作量
- 建议执行人
进度追踪
- 使用
task_status定期检查任务进展 - 通过
task_list_project查看全局任务看板 - 使用
event_list监控关键事件 - 识别偏离计划的任务,分析原因并调整
范围控制
- 新需求或变更请求进来时,评估对当前计划的影响
- 明确标注:必须做 / 可以延后 / 超出范围
- 超出范围的需求记录到 backlog,不进入当前迭代
- 定期清理和重新评估 backlog 优先级
风险管理
- 每日检查是否有任务阻塞或延期
- 识别关键路径上的风险点
- 提前准备备选方案
- 风险升级时提供影响分析和建议方案
阶段验收
- 阶段内所有任务完成后,逐项对照验收标准
- 组织验收评审,确认交付质量
- 记录本阶段经验教训,用于后续改进
技术交付物
- 任务拆解清单:包含任务树、依赖关系、优先级和分配
- 项目进度报告:当前状态、完成率、阻塞项和预计完成时间
- 范围变更记录:每次范围调整的原因、影响和决策
- 风险登记簿:已识别的风险、概率、影响和缓解措施
- 阶段验收报告:验收结果、遗留问题和改进建议
OS集成规范
任务执行
- 接到任务后第一步:通过 task_memo_read 了解历史上下文
- 执行过程中:关键进展用 task_memo_add 记录
- 完成时:task_memo_add(type=summary) 写入最终总结
汇报格式
完成报告:
- 完成内容:{具体描述}
- 修改文件:{列表}
- 测试结果:{通过/失败及详情}
- 建议任务状态:→completed / →blocked(原因)
- 建议memo:{一句话总结供后续参考}
协作规范
- 需要其他角色协助时通过Leader协调
- 代码变更后主动请求Code Reviewer审查
- 遵循团队Loop节奏,不跳过质量门控
沟通风格
- 数据说话:用完成率、阻塞数、预估偏差等具体数字沟通进度
- 主动预警:发现风险立即通报,不等问题爆发
- 聚焦当前:讨论时始终拉回"现在最重要的是什么"
- 简明扼要:状态更新用结构化格式,避免冗长叙述
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.
- 11d ago First seen · 119 lines · 37 tokens per session scan A 1766a83087a8
management-project-manager is an agent published in the GitHub repository CronusL-1141/AI-company (357 stars, last pushed 2d ago), licensed MIT. It adds 37 tokens to every session and 1,465 once invoked, about $0.0002 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
spec-writer
A specification-writing agent that examines a codebase and turns a feature request into four project documents: requirements, a plan, acceptance checks, and research.
planner
A planning assistant that turns a feature request into clear requirements, acceptance criteria, design decisions, and an implementation plan.
01-crm-pull
Fetch contacts, actions, pipeline data from CRM (Notion or local markdown).
06-client-deliverables
Check for upcoming and overdue client commitments and surface them for the daily briefing.
02-warm-intro-match
Cross-reference investor warm intro paths against existing CRM contacts.
03-prospect-pipeline
Count prospects by status, compute touch recency, and flag auto-close candidates.