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-task)<a href="https://agentmods.dev/commands/cronusl-1141/ai-company/os-task"><img src="https://agentmods.dev/badge/commands/cronusl-1141/ai-company/os-task/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-task"><img src="https://agentmods.dev/badge/commands/cronusl-1141/ai-company/os-task.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.00018 | $0.00603 |
| Opus 5.5 | $0.00007 | $0.00241 |
| Sonnet 5.5 | $0.00004 | $0.00121 |
| Haiku 4.5 | $0.00002 | $0.00060 |
Grade A, and why
os-task 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 29d 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-task — 任务管理
帮助用户管理 AI Team OS 的任务墙。
用法
/os-task— 查看当前项目的任务墙/os-task <team_id|团队名>— 只看某支队的任务墙/os-task new <描述>— 把一件事放上任务墙/os-task <task_id>— 查看单个任务详情与进展记录
操作流程
无参数：看任务墙
调用 task_list_project()（不传参即用当前活跃项目），先原样展示返回开头的
digest：全墙统计（未关条数按状态 × 期限、近 7 天新建与关闭、停滞与沉底计数）、
最近动静 5 条、待办最优先 5 条、中长期待办之首。用户要看更多再展开 wall：
按 short/mid/long 分组，每组先是一页待办（按分数，同分先上墙的在前；not_shown
是这一页没列出的待办条数），再是全部进行中、阻塞、失败的任务。
只看一支队时传 task_list_project(team_id="<队名或ID>")。
new 模式：把任务放上墙
- 确认两件事（用户已给出就不要再问）：任务描述、目标团队。
团队用
team_list()取；只有一支活跃队就直接用它。 - 调用
task_create(...)；若要立刻挂到某支队名下并带优先级/时间档， 用task_run(team_id=..., description=..., priority=..., horizon=...)。 - 任务上墙 ≠ 有人在做：OS 不会自己执行任务。要推进就用 CC 的
Agent(...)派人，并在 prompt 里写明 task_id，让其用task_memo_add回写进展。
查看模式：任务详情
task_status(task_id)— 状态、归属、依赖、结果。task_memo_read(task_id)— 历史进展记录（接手前必读）。- 想看完整时间线：
task_execution_trace(task_id)；要连带耗时/步数统计就task_execution_trace(task_id, include_stats=True)。
注意
- 状态用中文标记：pending=待处理, running=进行中, blocked=被阻塞, completed=已完成, failed=失败
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.
- 29d ago Changed · +2 lines be55d6b5314a
- 1mo ago Changed · -27 lines b401a78ec08c
- 2mo ago First seen · 74 lines · 18 tokens per session scan A d91606f97a47
os-task is a command published in the GitHub repository CronusL-1141/AI-company (375 stars, last pushed 3d ago), licensed MIT. It adds 18 tokens to every session and 603 once invoked, about $0.0001 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-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/.
gsd-plan-phase
Create detailed phase plan (PLAN.md) with verification loop.
gsd-audit-milestone
Audit milestone completion against original intent before archiving.
gsd-autonomous
Run all remaining phases autonomously — discuss→plan→execute per phase.