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-github-pr-reviewnpx skills add rpamis/comet --skill comet-github-pr-reviewgit 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-github-pr-review)<a href="https://agentmods.dev/skills/rpamis/comet/comet-github-pr-review"><img src="https://agentmods.dev/badge/skills/rpamis/comet/comet-github-pr-review.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.00069 | $0.00607 |
| Opus 5 | $0.00034 | $0.00303 |
| Sonnet 5 | $0.00014 | $0.00121 |
| Haiku 4.5 | $0.00007 | $0.00061 |
Grade A, and why
comet-github-pr-review 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 4d 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 GitHub PR 审阅
先读取 ../comet-github/references/maintainer-contract.md。除非用户另行授权修复或回复 GitHub，否则保持只读。
刷新目标状态
- 解析 PR 编号或 URL，并确认仓库。
- 获取当前 PR 元数据：目标分支、源分支和 SHA、作者、关联 Issue、标签、可合并状态和更新时间。
- 阅读完整 PR 正文、提交、diff、评论和 review thread。确认 thread 是否已解决或过期，不要把所有可见评论都当作仍然有效。
- 查询准确 head 对应的当前检查。如果有失败检查，将详细调查交给
comet-github-ci-triage。
结论必须基于当前 PR head/base。测试通过不能证明 PR 可合并，因为 head 可能落后于 base 或存在当前冲突。
审阅实现
针对每个声明的行为：
- 找到真实的生产调用路径；
- 将实现与关联 Issue/spec 对照；
- 必要时检查相关测试和生成 Runtime 资产；
- 报告 Bug 或阻塞项时复现可达的失败路径；
- 检查当前 head 是否已经修复该问题。
Review bot 输出只能作为调查线索，不能直接作为结论。区分生产逻辑、测试/fixture 漂移、生成物漂移、环境噪音和合并冲突。
只报告必须处理的问题
优先报告会阻塞正确性、数据完整性、安全、用户可见行为或合并的问题。除非仓库契约明确要求，否则省略纯风格建议、理论边界和推测性改进。
每个问题包含：严重程度、简洁标题、准确的文件/行号或 Runtime 路径、当前行为为何失败、最小修正方向以及证据状态。
结尾给出明确结论，例如“没有必须修复项”“存在必须修复项”“需要先处理合并/CI 问题”或“证据不足”。
评论和修复边界
- 用户要求评论时，在分析后提供可直接复制的 Markdown。
- 未经明确要求不得发布评论。
- 用户要求修复时，将已确认范围交给
comet-github-issue-fix或现有 Comet workflow；不要基于未确认的 bot 建议直接修改。
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.
- 4d ago First seen · 45 lines · 69 tokens per session scan A 3666872b3674
comet-github-pr-review is a skill published in the GitHub repository rpamis/comet (2,914 stars, last pushed today), licensed MIT. It adds 69 tokens to every session and 607 once invoked, about $0.0003 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.
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.…
codex-setup
Initialize sd0x-dev-flow infrastructure for Codex CLI and other non-Claude agents. Generates AGENTS.md, installs the commit-msg hook, copies runner scripts. The pre-push gate is opt-in via --with-push-gate. Use when setting up a new project or after updating skills.