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-issue-triagenpx skills add rpamis/comet --skill comet-github-issue-triagegit clone --depth 1 https://github.com/rpamis/cometWhat 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.00066 | $0.00524 |
| Opus 5 | $0.00033 | $0.00262 |
| Sonnet 5 | $0.00013 | $0.00105 |
| Haiku 4.5 | $0.00007 | $0.00052 |
Grade A, and why
comet-github-issue-triage 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.
What it actually says
Comet GitHub Issue 分诊
先读取 ../comet-github/references/maintainer-contract.md。除非用户明确授权 GitHub 或代码变更，否则保持只读。
收集当前证据
- 阅读完整 Issue 正文、评论、标签、作者、时间、关联 PR 和此前的分诊记录。
- 按领域概念搜索已有 Issue，而不只是复用报告者的原文措辞。识别重复、被替代的 Issue 和已经实现的行为。
- 检查当前源码、配置、安装路径、生成资产和相关测试，以实际仓库契约作为判断依据。
- Bug 信息充分时复现最小有效路径。环境或凭证问题需要区分本地设置和产品行为。
不要仅因描述听起来合理就认定存在缺陷。报告可能有效、夸大、过期，或由本地安装/配置不一致造成。
分类结果
选择一个主要分类：
confirmed defect：当前行为违反用户可见行为或仓库契约，且证据能定位路径；likely defect：证据较强，但仍缺少复现或决定性边界；configuration/install issue：产品行为正确，或本地安装已过期/配置错误；duplicate/already implemented：行为或 Issue 已在其他位置存在；insufficient information：需要补充具体步骤、版本、日志、平台或项目状态；feature request：请求的是新能力，而不是回归问题。
报告与下一步
返回分类和置信度、检查过的证据、相关代码/Runtime 路径、已确认和未知的内容，以及建议动作：补充信息、本地修复、创建聚焦 follow-up、关联已有 PR，或按重复/已实现处理。
不得自动关闭、加标签、评论或创建 follow-up Issue。确实需要新 Issue 时，用户确认范围后再交给 comet-github-idea-to-issue 起草。
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 First seen · 36 lines · 66 tokens per session scan A 313ce93c4516
comet-github-issue-triage is a skill published in the GitHub repository rpamis/comet (2,902 stars, last pushed yesterday), licensed MIT. It adds 66 tokens to every session and 524 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-wiki
Use when initializing, checking, enriching, or reviewing agent-spec code live wiki pages, sourcefiles trace, or Rust architecture inventory.
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.