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-safe-deliverygit 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-safe-delivery)<a href="https://agentmods.dev/skills/rpamis/comet/comet-safe-delivery"><img src="https://agentmods.dev/badge/skills/rpamis/comet/comet-safe-delivery.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.1 | $0.00078 | $0.00503 |
| Opus 5 | $0.00039 | $0.00251 |
| Sonnet 5 | $0.00016 | $0.00101 |
| Haiku 4.5 | $0.00008 | $0.00050 |
Grade A, and why
comet-safe-delivery 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 7d 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
Comet 安全交付
先读取 ../comet-github/references/maintainer-contract.md。只有用户明确授权后才执行 Git 交付动作；本 Skill 永远不会发布到 npm。
交付前检查
- 记录当前分支、upstream、
git status --short --branch和git worktree list --porcelain。 - 检查 diff，确定准确的目标路径。如果与无关改动重叠，先确认范围。
- 确认目标分支和 remote，不要静默切换分支或改变交付目标。
- 涉及子模块时，先确认子模块自己的分支/状态；得到授权交付时，先提交子模块，再更新父仓库 gitlink。
暂存与验证
- 只暂存明确的目标路径；混合工作区中不要使用宽泛的暂存命令。
- 检查
git diff --cached --name-status、git diff --cached --stat和git diff --cached --check。 - 让仓库 pre-commit hook 正常运行。如果 hook 修改了暂存内容，重新检查暂存文件名和 diff。
- 使用带类型前缀的提交信息，例如
fix: ...、docs: ...或chore: ...。
交付
只提交已确认的暂存范围，只推送用户明确指定的分支和 remote。完成后验证本地状态、commit SHA、upstream 关系和远端分支 SHA。分别报告 commit、push 和线上 CI 状态。
除非另行要求，不创建 PR、不合并远端分支、不删除分支、不移除 worktree、不改写历史。删除 worktree 或分支前，确认关联关系、准确目标和可恢复性；不得强制删除宽泛或未解析的路径。
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.
- 7d ago First seen · 30 lines · 78 tokens per session scan A b1dcb4580f91
comet-safe-delivery is a skill published in the GitHub repository rpamis/comet (2,937 stars, last pushed today), licensed MIT. It adds 78 tokens to every session and 503 once invoked, about $0.0004 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
git-workflow-and-versioning
Structures git workflow practices. Use when making any code change. Use when committing, branching, resolving conflicts, opening or reviewing a pull request (PR), pushing to a remote, or when you need to organize work across multiple parallel streams. Use when cutting a release, choosing a semantic version bump…
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).
next-step
Change-aware next step advisor. Use when: user asks what to do next, workflow progression is unclear, session just started with dirty worktree. Not for: executing the suggested command (user decides), auto-loop decisions (hooks handle that). Output: findings-based suggestions or session summary with commit seed.
precommit
Pre-commit checks — lint:fix -> build -> test.
precommit-fast
Quick pre-commit checks — lint:fix -> test.
bump-version
A procedure for changing a package and plugin version in several project files at the same time.