OpenMOSS is an operating system for teams of AI agents: it organizes agents into roles that plan, execute, review, and monitor work autonomously. It is for running recurring, multi-step tasks with little or no human coordination. The catalogue skills and agents extend the team’s abilities and workflows.
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.
npx skills add uluckyXH/OpenMOSS --skill task-planner-skillgit clone --depth 1 https://github.com/uluckyXH/OpenMOSSWrote 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/skills/uluckyxh/openmoss/task-planner-skill)<a href="https://agentmods.dev/skills/uluckyxh/openmoss/task-planner-skill"><img src="https://agentmods.dev/badge/skills/uluckyxh/openmoss/task-planner-skill/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/skills/uluckyxh/openmoss/task-planner-skill"><img src="https://agentmods.dev/badge/skills/uluckyxh/openmoss/task-planner-skill.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00027 | $0.01004 |
| Opus 5.5 | $0.00011 | $0.00402 |
| Sonnet 5.5 | $0.00005 | $0.00201 |
| Haiku 4.5 | $0.00003 | $0.00100 |
Grade A, and why
task-planner-skill 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.
How it starts
The opening of the file, as written. The whole thing — 105 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Task Planner Skill
你可以使用 task-cli.py 工具来管理任务系统。该工具位于本 Skill 目录下。
认证信息
- API_KEY:
<注册后填入>
工作流程
- 获取规则 → 2. 检查积分 → 3. 查看/创建任务 → 4. 创建模块 → 5. 创建子任务并分配 → 6. 收尾交付 → 7. 记录日志
可用命令
所有命令前缀：
python task-cli.py --key <API_KEY>
规则
rules # 获取合并后的规则提示词（执行前必须调用）
任务管理
task list # 查看所有任务
task list --status active # 按状态过滤
task create "任务名" --desc "描述" --type once # 创建任务
task get <task_id> # 查看任务详情
task edit <task_id> --name "新名" --desc "新描述" # 编辑任务（仅 planning/active）
task status <task_id> active # 更新任务状态
task cancel <task_id> # 取消任务
模块管理
module list <task_id> # 查看任务下的模块
module create <task_id> "模块名" --desc "描述" # 创建模块
子任务管理
st list --task-id <task_id> # 查看某任务下的子任务
st list --status blocked # 查看被标记 blocked 的子任务
st create <task_id> "子任务名" --deliverable "交付物" --acceptance "验收标准" --assign <agent_id>
st get <sub_task_id> # 查看子任务详情
st edit <sub_task_id> --name "新名" --acceptance "新标准" # 编辑子任务（仅 pending/assigned）
st cancel <sub_task_id> # 取消子任务
st reassign <sub_task_id> <agent_id> # 重新分配（blocked → assigned）
📄 列表命令默认返回全部数据。如数据较多，可加
--page N --page-size M分页查看。返回结果包含total（总数）和has_more（是否还有更多）。
Agent 查看
agents # 查看已注册 Agent（ID、角色、状态、积分）
agents --role executor # 按角色过滤
积分
score me # 查看自己的积分
score logs --page 1 --page-size 10 # 查看积分明细（建议分页，避免数据过多）
score agent-logs <agent_id> --page 1 --page-size 10 # 查看指定 Agent 的积分明细
score leaderboard # 积分排行榜，分配时参考
📄
score logs默认返回全部明细。如数据较多，可加--page N --page-size M分页查看。
通知
notification # 查看通知渠道配置
日志
log create "plan" "规划了xxx任务，分配给了xxx"
log mine # 回顾工作记录（默认最近7天，最多20条）
log mine --action reflection # 只看自省笔记
log list --sub-task-id <id> # 查看某子任务的所有日志
log list --action blocked --days 3 # 扫描执行者求助日志
log list --days 30 --limit 50 # 最近30天，最多50条
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 First seen · 105 lines · 27 tokens per session scan A 5b4ebda875bb
task-planner-skill is a skill published in the GitHub repository uluckyXH/OpenMOSS (1,333 stars, last pushed 4mo ago), licensed MIT. It adds 27 tokens to every session and 1,004 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 skills, from other repositories
story-readiness
Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
qa-project-bootstrap
Onboard a new QA engineer to an existing codebase, or audit an existing test architecture. Produces a 30-day ramp plan: codebase orientation, framework walkthrough, test architecture audit, mentorship pairing, and first-test guidance. Use when: "QA onboarding," "new tester," "ramp up," "test architecture audit,"…
handle-linkedin-connection-request-signal
Use this skill when someone sends a team member an inbound LinkedIn connection request. An inbound request is a deliberate, ACTIVE first-party intent signal — meaningfully stronger than a passive profile view — and it deserves different scoring rules. The skill resolves and enriches the requester, gates them through…