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 agentmods add skills/marsz42/orbitos/kickoffnpx skills add MarsZ42/OrbitOS --skill kickoffgit clone --depth 1 https://github.com/MarsZ42/OrbitOSWrote 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/marsz42/orbitos/kickoff)<a href="https://agentmods.dev/skills/marsz42/orbitos/kickoff"><img src="https://agentmods.dev/badge/skills/marsz42/orbitos/kickoff.svg" alt="Measured on agentmods" 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 | $0.00016 | $0.01566 |
| Opus 5 | $0.00008 | $0.00783 |
| Sonnet 5 | $0.00003 | $0.00313 |
| Haiku 4.5 | $0.00002 | $0.00157 |
Grade A, and why
kickoff 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 5d 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 — 172 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the Project Manager orchestrator for OrbitOS. When the user wants to kickoff a project, you coordinate two specialized agents: one for planning and one for execution.
Workflow Overview
This skill uses two separate agents to keep context fresh and focused:
- Planning Agent: Gathers context, designs project structure, creates the plan file
- Orchestrator (you): Coordinates agents and waits for user confirmation
- Execution Agent: Creates the project note with fresh context (reads only the plan file)
Your Role as Orchestrator
- When
/kickoffis invoked, spawn the planning agent - Planning agent creates the plan file and returns the path
- Notify the user to review the plan
- When user confirms, spawn the execution agent with just the plan file path
- Report back the execution agent's results
Input Context
The user can provide input in three ways:
- File path: A path to an inbox note (e.g.,
/kickoff 00_收件箱/MyIdea.md) - read the file contents - Inline text: A short description of a project idea (e.g.,
/kickoff Build a habit tracker app) - No input: If nothing provided, list files from
00_收件箱/and ask the user to select one
Language Rule: Match the language of the user's input (or inbox file content) for all responses and generated files.
Phase 1: Launch Planning Agent
When the user invokes /kickoff with their idea, immediately spawn a planning agent using the Task tool:
subagent_type: "general-purpose"
description: "Plan project kickoff"
prompt: "Create a project kickoff plan for: [user's idea/inbox note]
Follow these steps:
1. Gather Context: Search 20_项目 and 10_日记 for existing notes related to this idea
2. Identify the relevant Area (SoftwareEngineering, Finance, Health, Writing, etc.)
3. Create the plan file at 90_计划/Plan_YYYY-MM-DD_Kickoff_<ProjectName>.md using this format:
# 启动计划: [项目名称]
## 来源
- 收件箱文件: [收件箱文件路径(如适用),或"内联输入"]
## 目标
[一句话总结项目目标]
## 项目结构
- 领域: [来自 30_研究 的相关领域]
- 类型: [project]
- 预估规模: [小型: 单文件 | 中型: 少量文件的文件夹 | 大型: 多文件的文件夹]
## 建议行动项
[ ] 定义成功标准
[ ] 分解为阶段/里程碑
[ ] 识别依赖项或阻碍因素
[ ] 设置项目文件夹结构
## 项目大纲草案
### 背景
[这解决什么问题,为什么重要]
### 行动(阶段)
- 阶段1: [描述]
- 阶段2: [描述]
### 成功指标
- [ ] 指标1
- [ ] 指标2
## 澄清问题(可选)
*如果你有答案,请在下方填写。如果留空,我将按标准假设继续。*
**问:** 这个项目的时间线/截止日期是什么?
**答:**
**问:** 优先级是多少?(P0=紧急, P1=高, P2=中, P3=低, P4=以后)
**答:**
**问:** 有任何特定的约束或要求吗?
**答:**
4. Return the path to the created plan file.
"
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.
- 5d ago First seen · 172 lines · 16 tokens per session scan A eb424c64c6a4
kickoff is a skill published in the GitHub repository MarsZ42/OrbitOS (968 stars, last pushed 5mo ago), licensed MIT. It adds 16 tokens to every session and 1,566 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…