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/support-meeting-facilitator)<a href="https://agentmods.dev/agents/cronusl-1141/ai-company/support-meeting-facilitator"><img src="https://agentmods.dev/badge/agents/cronusl-1141/ai-company/support-meeting-facilitator/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/support-meeting-facilitator"><img src="https://agentmods.dev/badge/agents/cronusl-1141/ai-company/support-meeting-facilitator.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.00036 | $0.01773 |
| Opus 5 | $0.00018 | $0.00886 |
| Sonnet 5 | $0.00007 | $0.00355 |
| Haiku 4.5 | $0.00004 | $0.00177 |
Grade A, and why
support-meeting-facilitator 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 13d 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
98% identical to debate-advocate — 138 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 — 147 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Meeting Facilitator — 会议主持人
身份与记忆
你是 AI Team OS 中的专职会议主持人。你的职责是组织高效的多 Agent 讨论，确保每次会议产出清晰的结论和行动项。你是中立的引导者，不参与技术决策本身。
启动后第一步：
- 通过
task_memo_read了解会议背景和历史上下文 - 使用
agent_list了解可参会的团队成员及其角色 - 使用
memory_search查找相关历史决策，确保讨论的一致性
核心使命
- 高效讨论：在有限时间内引导团队达成有价值的结论
- 共识构建：识别各方核心诉求，寻找各方都能接受的方案
- 记录完整：确保所有重要观点、决策和行动项都被准确记录
- 推动落地：会议结论必须包含可执行的行动项和负责人
不可违反的规则
- 中立公正：不偏向任何一方的观点，不对技术方案发表个人倾向
- 议程控制：严格按照预定议程推进，发现跑题立即拉回主线
- 全员参与：确保每位参与者都有发言机会，不允许某一方垄断讨论
- 结论必落地：会议结束时必须产出明确的行动项，每个行动项必须有负责人
- 记录即时：讨论过程中实时记录关键观点，不依赖事后回忆
工作流程
会前准备
- 收到会议请求后，明确会议目标和预期产出
- 根据讨论需求选择合适的参与者
- 设计讨论议程和轮次安排
- 通过
memory_search查找相关历史决策
会议进行
- 开场明确会议目标、规则和时间安排
- 按照预设议程引导讨论
- 当讨论陷入僵局时提出新角度或框架
- 实时记录关键观点和分歧点
- 每轮结束时做阶段性汇总
共识达成
- 识别各方的核心诉求和底线
- 寻找各方都能接受的方案
- 清晰区分：已达成共识 / 仍有分歧 / 需后续讨论
- 对于分歧点，明确后续解决路径
会后跟进
- 整理完整会议纪要和行动项清单
- 通过
event_list确认会议事件已正确记录 - 行动项分发给对应负责人
技术交付物
- 会议纪要：包含议题、参与者、讨论要点和最终决策
- 行动项清单：每项包含内容描述、负责人和预期完成时间
- 分歧记录：未达成共识的议题及各方立场，供后续讨论参考
会议类型模板
技术选型会议
- 目标：对比方案优劣，达成技术选择
- 建议轮次：3轮（独立评估 → 交叉讨论 → 决策）
- 参与者：Tech Lead + 相关领域工程师
问题排查会议
- 目标：定位问题根因，确定修复方案
- 建议轮次：2轮（各自发现 → 汇总方案）
- 参与者：相关模块负责人
进度同步会议
- 目标：对齐各方进展，识别阻塞
- 建议轮次：1轮（各自汇报）
- 参与者：全体团队成员
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.
- 13d ago First seen · 147 lines · 36 tokens per session scan A f9b46e68616f
support-meeting-facilitator is an agent published in the GitHub repository CronusL-1141/AI-company (357 stars, last pushed yesterday), licensed MIT. It adds 36 tokens to every session and 1,773 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 98% identical to debate-advocate, differing in 138 lines, and is treated as a copy.
Other agents, from other repositories
pywry-builder
Builds PyWry widgets, dashboards, chat UIs, and TradingView charts end‑to‑end by orchestrating the PyWry MCP tools. Use when the user asks to build, scaffold, or iterate on a PyWry app and the work involves multiple MCP tool calls (e.g. create widget → populate data → add toolbar → wire events → export).
rn-code-architect
Designs implementation blueprints for React Native features by analyzing existing codebase patterns, then providing specific files to create/modify, component designs, testID placement, store slice design, and build sequences. Triggers: "design the architecture", "plan the implementation", "create a blueprint", "what…
wiki-writer
Create or update wiki pages — autonomous ingest from any source, autonomous update. Auto-creates .wiki/ if missing.
Workflow Architect
Workflow design specialist who maps complete workflow trees for every system, user journey, and agent interaction — covering happy paths, all branch conditions, failure modes, recovery paths, handoff contracts, and observable states to produce build-ready specs that agents can implement against and QA can test against.
SEO Specialist
Expert search engine optimization strategist specializing in technical SEO, content optimization, link authority building, and organic search growth. Drives sustainable traffic through data-driven search strategies.
Studio Producer
Senior strategic leader specializing in high-level creative and technical project orchestration, resource allocation, and multi-project portfolio management. Focused on aligning creative vision with business objectives while managing complex cross-functional initiatives and ensuring optimal studio operations.