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/commands/cronusl-1141/ai-company/os-meeting)<a href="https://agentmods.dev/commands/cronusl-1141/ai-company/os-meeting"><img src="https://agentmods.dev/badge/commands/cronusl-1141/ai-company/os-meeting/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/commands/cronusl-1141/ai-company/os-meeting"><img src="https://agentmods.dev/badge/commands/cronusl-1141/ai-company/os-meeting.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.00011 | $0.00488 |
| Opus 5 | $0.00005 | $0.00244 |
| Sonnet 5 | $0.00002 | $0.00098 |
| Haiku 4.5 | $0.00001 | $0.00049 |
Grade A, and why
os-meeting 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 12d 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.
What it actually says
/os-meeting — 会议管理
你需要帮助用户创建或管理 AI Team OS 中的会议。
用法
用户可以通过以下方式调用：
/os-meeting— 显示活跃会议列表/os-meeting create <主题>— 创建新会议/os-meeting <meeting_id>— 查看指定会议详情和消息
操作流程
无参数：列出活跃会议
- 调用
team_list获取所有团队 - 对每个团队调用
meeting_list（status=active） - 以表格形式展示活跃会议
create 模式：创建新会议
- 向用户确认：
- 会议主题（如果用户已提供则直接使用）
- 目标团队（如只有一个团队则自动选择）
- 参与者列表（调用
agent_list展示可选 Agent）
- 调用
meeting_create创建会议 - 显示会议操作指引：
- 发送消息的 API 调用方式
- 讨论规则: R1各自观点 → R2+引用回应 → 最后汇总共识
查看模式：查看会议详情
- 调用
meeting_get获取会议信息 - 调用
meeting_messages获取消息列表 - 按轮次分组展示消息
输出格式
会议列表
## 活跃会议
| 会议ID | 主题 | 参与者 | 消息数 | 团队 |
|--------|------|--------|--------|------|
| abc123 | 架构讨论 | 3人 | 12条 | dev-team |
会议详情
## 会议: <主题>
状态: 活跃 | 参与者: A, B, C
### Round 1
**AgentA**: 发言内容...
**AgentB**: 发言内容...
### Round 2
**AgentA**: 发言内容...
注意
- 所有输出使用中文
- 创建会议前确认参与者列表
- 显示会议消息时按 round_number 分组
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.
- 12d ago First seen · 71 lines · 11 tokens per session scan A 8d564ea6daa8
os-meeting is a command published in the GitHub repository CronusL-1141/AI-company (357 stars, last pushed today), licensed MIT. It adds 11 tokens to every session and 488 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 commands, from other repositories
dashboard-session-fork
Fork a session into a new one. Usage /dashboard:session-fork.
dashboard-session-hide
Hide a session from the dashboard list. Usage /dashboard:session-hide.
exec-plan
Create, manage, and track execution plans as first-class repository artifacts in docs/exec-plans/.
hep-graph.body
A command for viewing saved Agentlas automation graphs and requesting that one be run. The desktop app performs the actual run.
r-status
Display a structured overview of project health: plan progress, phase outcomes, governance freshness, and recent activity.
r-tasks
Display the current task list state. Use this when a long-running command seems stuck, or to check progress at any time.