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.00012 | $0.00239 |
| Opus 5.5 | $0.00005 | $0.00096 |
| Sonnet 5.5 | $0.00002 | $0.00048 |
| Haiku 4.5 | $0.00001 | $0.00024 |
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 1mo 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 — 会议管理
用法
/os-meeting— 列活跃会议：meeting_list(status="active")/os-meeting <meeting_id>— 看某场会议：meeting_read_messages(meeting_id)，按round_number分组展示；要确认是否全员发过言用meeting_attendance_check(meeting_id)/os-meeting create <主题>— 走技能 meeting-facilitate，见下
create 必须走技能
meeting_create 只写库，不会拉任何一个 agent 到场。只调它就向用户汇报"会议已创建"，
出勤校验会显示 0 人发言，而你会去查 agent 为什么不说话——其实没人被 spawn 过。
选模板、spawn 真实参与者、签到、推进轮次、conclude 并把决策上墙，完整流程在技能 meeting-facilitate 里。
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.
- 1mo ago Changed · -49 lines · +1 tokens per session c7a1b42b12d9
- 1mo 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 (374 stars, last pushed 16d ago), licensed MIT. It adds 12 tokens to every session and 239 once invoked, about $0.0000 per session on Opus 5.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-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/.
gsd-autonomous
Run all remaining phases autonomously — discuss→plan→execute per phase.
gsd-plan-phase
Create detailed phase plan (PLAN.md) with verification loop.
gsd-insert-phase
Insert urgent work as decimal phase (e.g., 72.1) between existing phases.
hep-graph.body
A command for viewing saved Agentlas automation graphs and requesting that one be run. The desktop app performs the actual run.