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 agentmods add skills/rpamis/comet/comet-hotfixnpx skills add rpamis/comet --skill comet-hotfixgit 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-hotfix)<a href="https://agentmods.dev/skills/rpamis/comet/comet-hotfix"><img src="https://agentmods.dev/badge/skills/rpamis/comet/comet-hotfix.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.00029 | $0.03827 |
| Opus 5 | $0.00015 | $0.01913 |
| Sonnet 5 | $0.00006 | $0.00765 |
| Haiku 4.5 | $0.00003 | $0.00383 |
Grade A, and why
comet-hotfix 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 3d 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 — 215 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Comet 预设路径：Hotfix
开始或恢复前必须先读取并执行 comet-classic/reference/classic-layout.md；本文件中的 OpenSpec CLI 调用必须使用 adapter，文件路径必须使用该协议绑定的 <classic-*> 逻辑根。
快速 bug fix 工作流：open → build → 根因消除检查 → verify → archive。跳过 brainstorming 和完整 plan，适用于行为修复、不涉及新 capability 设计的场景。
适用条件（必须全部满足）：
- 修复已有功能的 bug，不新增 capability
- 不涉及接口变更或架构调整
- 改动范围可预估（文件数仅作提示，不作为硬性升级条件，见下方升级判定）
不适用：如修复过程命中质变信号（见「升级判定」章节），由用户决定是否升级为完整 /comet-classic 流程。
流程（预设流程，6 步）
0. 输出语言约束
精简版 OpenSpec 产物必须使用 Comet 配置产物语言。.comet.yaml 尚不存在时依次读取项目 .comet/config.yaml 和全局 ~/.comet/config.yaml 的 classic.language，初始化后使用 comet state get <name> language 读取。
执行链路：open → build → 根因消除检查 → verify → archive。Hotfix 为每个阶段提供默认决策：精简开启、直接构建、根因确认、按规模验证、验证通过后进入归档前最终确认。
开始前按 comet-classic/reference/scripts.md 运行公开 Comet CLI 命令；从任意入口恢复时先按 comet-classic/reference/context-recovery.md 检查 phase/workflow。
恢复已有 hotfix change 时，第一项状态操作必须是 comet state select <change-name>；创建新 change 时，在 .comet.yaml 初始化成功后立即运行该命令，再进入源码写入步骤。
进入 hotfix 工作区并读取当前状态 phase 后，运行 comet task <project-root> --task "<用户原始请求>" --phase "<phase>" --session "<本次任务稳定标识>" --json。只注入返回的 text；Context Manifest（manifest / <context_manifest>）只含摘要、应用原因和稳定 ID，需要正文、来源或验证方式时增加 --expand-context "<id>"，路径、操作或阶段变化时以同一 --session 重新选择。用户明确要求长期记住时调用 comet memory remember ... --scope global|project；仅对隐式但可复用的稳定协作方式调用 comet memory observe，不得保存任务摘要、进展、命令输出或测试结果。实际使用条目且结果明确后，用 applications[].applicationId（Hook 文本中的 application_id）运行 comet task <project-root> --task "<用户原始请求>" --application "<application-id>" --outcome used-successfully|ignored|overridden|corrected|contributed-to-failure --json。任务结束仍运行带 --complete --workflow <workflow> --change <change-id> 的 comet task。无 Hook 时由本 Skill 使用相同接口，comet memory context 只作为兼容入口；插件失败不阻断修复。
1. 快速开启（预设 open）
复用 Comet open 能力创建 change，但使用 hotfix 默认值：不执行 openspec-explore 长探索，直接进入精简 change 创建。
立即执行： 使用 Skill 工具加载 openspec-new-change 技能。禁止跳过此步骤。
外部 OpenSpec Skill 覆写： 加载后不得执行其中直接官方 CLI、固定 cwd 或固定物理 OpenSpec 路径的指令；所有 OpenSpec 命令改用 comet classic openspec -- <args...>，所有 change 与 artifact 路径改用本轮绑定的 <classic-*> 逻辑根。
What ships with it
1 file 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.
- 3d ago Changed · +2 lines 4de92db4812c
- 5d ago First seen · 213 lines · 29 tokens per session scan A a429313c07dd
comet-hotfix is a skill published in the GitHub repository rpamis/comet (2,927 stars, last pushed today), licensed MIT. It adds 29 tokens to every session and 3,827 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
agent-spec-tool-first
CRITICAL: Use for agent-spec CLI tool workflow. Triggers on: agent-spec, contract, lifecycle, guard, verify, explain, stamp, checkpoint, plan, requirements, work-units, knowledge requirements, KLL, docs vs knowledge, spec verification, task contract, spec quality, lint spec, run log, "how to verify", "how to use…
agent-spec-authoring
CRITICAL: Use for writing and editing agent-spec .spec/.spec.md files. Triggers on: write spec, create spec, edit spec, new spec, spec authoring, task contract, .spec file, .spec.md file, BDD scenario, acceptance criteria, completion criteria, test selector, boundary, constraint, intent, decision, out of scope, "how…
agent-spec-estimate
CRITICAL: Use for estimating work effort from agent-spec Task Contracts. Triggers on: estimate, estimation, how long, work effort, round count, time estimate, scope, sizing, cost, budget, planning, sprint, capacity, "how many rounds", "how long will this take", "estimate this spec", 估算, 工作量, 多久, 时间估算, 预估, 工时, 规模…
agent-spec-intent-compiler
Use when converting PRD or issue prose into KLL requirements, running the intent compiler plan, or reverse-interviewing a human to resolve requirement ambiguity before task spec generation.
push-ci
Push to remote and monitor CI. Validates branch safety, executes git push WITH explicit user approval, then monitors CI run status via gh CLI. Use when: user says 'push', 'push and watch CI', 'ship it', 'push-ci'. Not for: committing (use /smart-commit), creating PRs (use /create-pr), merging (use /merge-prep).
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.…