Comet is a resumable workflow and skill platform for coding tasks, covering requirements work as well as skill creation, evaluation, and release. It supports separate Native and Classic workflows and can coordinate implementation and verification across isolated Git worktrees. The catalogue contains skills and instructions that implement Comet-related 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 rpamis/comet --skill comet-buildgit clone --depth 1 https://github.com/rpamis/cometWrote 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/rpamis/comet/comet-build)<a href="https://agentmods.dev/skills/rpamis/comet/comet-build"><img src="https://agentmods.dev/badge/skills/rpamis/comet/comet-build/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/rpamis/comet/comet-build"><img src="https://agentmods.dev/badge/skills/rpamis/comet/comet-build.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Socket pass
- Snyk pass
- 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.00036 | $0.01647 |
| Opus 5.5 | $0.00014 | $0.00659 |
| Sonnet 5.5 | $0.00007 | $0.00329 |
| Haiku 4.5 | $0.00004 | $0.00165 |
Grade A, and why
comet-build 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 yesterday.
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 — 31 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Comet 阶段 3：计划与构建（Build）
首次进入阶段、交接给新 Agent 或上下文恢复后，读取并执行 任务上下文与产物语言，优先采用当前 continuation 或已领取 Action 的 contextRequest；同一阶段连续执行不重复获取。
收到入口返回的 layout 后，按 comet-classic/reference/classic-layout.md 确定各逻辑根对应的目录。当前上下文已有这份协议时，无需重复加载。本文件中的 OpenSpec CLI 调用均通过适配器执行，文件路径均基于已绑定的 <classic-*> 根目录，无需先额外运行 root show。
SDK Run 路径
首次进入当前 SDK 阶段、换 Agent 或恢复上下文时，读取阶段入口与恢复及该参考的当前阶段章节；本会话已有且仍有效时直接复用。下文按当前阶段执行；nextAction.kind 的恢复路由只适用于没有 continuation mode 的旧响应。
优先复用当前有效结果中的 agent.continuation / data.nextAction 与已绑定状态；只有冷恢复、外部状态变化或缺少必要信息时，才运行 comet state next <change-name> --json。data.runtimeFormat 为 sdk 时，只按本节推进 Run；SDK 方法参考的执行策略选项、计划内容要求、实施与审查方法仍适用，状态和证据通过本节命令提交。data.phase 必须为 build。已有有效 layout 与当前配置时直接复用；缺少时运行 comet state check <change-name> build --json；若 nextAction.kind 为 reconcile，运行 comet state check <change-name> build --recover --json 核对原 Action 的结果，在结果明确前不重发外部工作。
先核对有效配置中的 workflow 或当前 nextAction.stepId。tweak.build.* / workflow: tweak：立即执行： 使用 Skill 工具加载 comet-tweak 技能。禁止跳过此步骤。hotfix.build.* / workflow: hotfix：立即执行： 使用 Skill 工具加载 comet-hotfix 技能。禁止跳过此步骤。技能加载后，传入同一 change、工作区、phase、Run revision 和 continuation，从该预设的 SDK Build 步骤继续，不要求 full Design Doc 或完整计划，也不重跑 Open。旧 Run 的原始 Action 仍可能引用 comet-build，同样按此规则路由。已批准升级且当前步骤为 full.build.* 时，执行下列 full 路径。
full.build.configure待执行时，按 SDK 方法参考的 Build 章节核对已有选择，只补真正缺失的执行方式、TDD 和审查决定。将已确认的build_mode、tdd_mode、review_mode、subagent_dispatch和需要时的direct_override写入仓库内的临时 JSON；用户已明确选择这份完整配置时，运行comet state propose-build <change-name> --file <configuration-json> --confirmed一次保存提案与批准；尚未决定时运行comet state propose-build <change-name> --file <configuration-json>。仅在仍有待决定 Wait 时，从返回的data.wait.proposalHash保存<proposalHash>，向用户展示实际配置并按 decision-point.md 等待确认。确认或拒绝时运行comet state decide-build <change-name> --proposal-hash <proposalHash> --choice <approved|rejected>；拒绝后从新配置重新提案。恢复已有待决定 Wait 时复用原提案，不重复提问或新建配置 Action。full.build.plan待执行时，按 SDK 方法参考的 Build 章节创建或核对计划。计划引用当前 Design Doc 和 tasks.md，以<!-- comet-task-authority: <classic-task-authority-ref> -->及<!-- comet-task-ref:<task-id> -->映射任务，不能另建 checkbox。运行comet state submit-plan <change-name> --plan <plan-ref>提交计划及证据。只有用户明确要求写完计划暂停时加--pause；恢复plan-readyWait 时，必须等用户明确继续，再用该 Wait 的当前哈希运行comet state continue-plan <change-name> --proposal-hash <proposalHash>。计划或任务要求变化后不复用原批准。full.build.execute待执行时，按 SDK 方法参考的 Build 章节的已选方法实施、做任务级或分段审查并运行相关检查。任务实际完成且审查合格后勾选同一 tasks.md；任务 ID、勾选和协调进度使用共享参考中的state tasks、state task-complete、state checkpoint；这些命令不推进 SDK Run。SDK 不调用旧comet handoff --write。核对计划、任务和工作区后运行comet state complete-build <change-name> --session <builder-execution-ref>，由 Run 进入检查 Action。实现或计划与已接受证据不一致时先解决具体漂移，不绕过 SDK 校验。full.build.check待执行时，以当前工作区中明确的完整构建或验收入口运行comet guard <change-name> build --apply -- <program> [args...]。此处没有新的用户决定，--apply会重新校验当前任务、配置、工作区和证据，再执行真实检查并向同一 Run 提交收据；仅在检查成功且证据仍有效时进入 Verify。仅在需要诊断时运行comet guard <change-name> build只读预检。若收据提交中断，先核对同一 Action 和检查记录，按 Guard 的恢复结果补交，不重新执行已完成的外部检查。失败后按返回的当前 Build Action 修复并重新验证；结果未提供 continuation 时再读state next --json。
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- yesterday Changed · -182 lines 8bd40ba5679b
- 20d ago Changed · -2 lines 0a5a5c7f0c92
- 1mo ago Changed · +6 lines fc872c47814e
- 1mo ago Changed · -81 lines · +11 tokens per session 4ab75817adb1
- 1mo ago Changed · -18 lines f0418c5cbaf1
- 1mo ago First seen · 308 lines · 25 tokens per session scan A f607114a87f4
comet-build is a skill published in the GitHub repository rpamis/comet (3,227 stars, last pushed yesterday), licensed MIT. It adds 36 tokens to every session and 1,647 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
create-request
Create, update, or scan per-task request tickets for progress tracking. These are date-prefixed non-lifecycle docs under requests/, NOT feature-level requirements (use /req-analyze for those). Use when: tracking task progress, updating completion status, scanning incomplete requests, checking request status dashboard.…
req-analyze
A requirements-analysis tool that breaks a problem into needs, stakeholders, and priorities before a technical solution is chosen.
recap-ask
Interactive Q&A over an existing recap document. Use when: user wants to ask follow-up questions about a briefing-recap- .md produced by /recap-doc, with recap-bounded context + out-of-scope redirect + optional promote-to-request. Not for: generating a new recap (use /recap-doc), general project Q&A (use /ask), code…
recap-doc
Post-development recap document generator. Use when: AI/Codex has implemented a feature and the user needs a guided walkthrough of what changed and why, with blind-spot detection and anticipated questions. Not for: Q&A follow-up (use /recap-ask), technical share-out for teammates (use /tech-brief), or generic code…
runbook
Generate and update feature release runbooks from existing docs and codebase. Use when: creating operational runbook, release handbook, deployment checklist, pre-release preparation. Not for: incident response (v2), code review (use codex-code-review), architecture design (use architecture).
jira
Jira integration — view issues, generate branches, create tickets, transition status. Use when: user mentions Jira ticket key (XX-123), says /jira, wants to create branch from ticket, create a new ticket, or update Jira status. Not for: GitHub issues (use issue-analyze).