comet-github-issue-triage

comet-github-issue-triage is a skill for Claude Code, Codex from rpamis/comet. It costs 66 tokens per session (524 once invoked), scanned A, original, MIT.

A read-only workflow for checking and classifying Comet GitHub Issues, which are reports or requests about a software project. It compares each report with the repository’s code, tests, configuration, installation behavior, and existing issues.

In plain words
What is it for?
Use it to investigate whether an issue is valid, reproduce a bug when possible, identify related issues or pull requests, and report evidence, confidence, unknowns, and a recommended next step.
Why use it?
It helps distinguish real, reproducible defects from duplicates, already-fixed behavior, feature requests, missing details, or local setup problems. This avoids closing or changing issues based only on an initial description.

Skill for Claude CodeCodex

Written for Claude Code and Codex: disable-model-invocation in frontmatter, but also agents/openai.yaml present.

Good fit Use it to investigate whether an issue is valid, reproduce a bug when possible, identify related issues or pull requests, and report evidence, confidence, unknowns, and a recommended next step.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/rpamis/comet/comet-github-issue-triage
About the project

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.

rpamis/comet · 3,255 stars · on GitHub · docs.comet.rpamis.com

Install

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.

Any agent
npx skills add rpamis/comet --skill comet-github-issue-triage
Clone the repo
git clone --depth 1 https://github.com/rpamis/comet

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for comet-github-issue-triage

README.md
[![agentmods](https://agentmods.dev/badge/skills/rpamis/comet/comet-github-issue-triage/github.svg)](https://agentmods.dev/skills/rpamis/comet/comet-github-issue-triage)
Your own site
<a href="https://agentmods.dev/skills/rpamis/comet/comet-github-issue-triage"><img src="https://agentmods.dev/badge/skills/rpamis/comet/comet-github-issue-triage/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.

agentmods 80×15 button for comet-github-issue-triage

Your own site · 80×15
<a href="https://agentmods.dev/skills/rpamis/comet/comet-github-issue-triage"><img src="https://agentmods.dev/badge/skills/rpamis/comet/comet-github-issue-triage.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 66 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 524 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00066 $0.00524
Opus 5.5 $0.00026 $0.00210
Sonnet 5.5 $0.00013 $0.00105
Haiku 4.5 $0.00007 $0.00052

Measured 2mo ago against content hash 313ce93c4516, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 2mo 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.

assets/skills-maintainer/comet-github-issue-triage/SKILL.md · 36 lines

What it actually says

Comet GitHub Issue 分诊

先读取 ../comet-github/references/maintainer-contract.md。除非用户明确授权 GitHub 或代码变更,否则保持只读。

收集当前证据

  1. 阅读完整 Issue 正文、评论、标签、作者、时间、关联 PR 和此前的分诊记录。
  2. 按领域概念搜索已有 Issue,而不只是复用报告者的原文措辞。识别重复、被替代的 Issue 和已经实现的行为。
  3. 检查当前源码、配置、安装路径、生成资产和相关测试,以实际仓库契约作为判断依据。
  4. 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 起草。

Files

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.

Changes

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.

  1. 2mo ago First seen · 36 lines · 66 tokens per session scan A 313ce93c4516

Subscribe to this mod's changes

comet-github-issue-triage is a skill published in the GitHub repository rpamis/comet (3,255 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.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.

Related

Other skills, from other repositories

issue-analyze

GitHub Issue and PR review thread deep analysis with Codex blind verdict. Use when: analyzing issue root cause, classifying problems, investigation planning, triaging PR review comments for actionability. Not for: fixing bugs (use bug-fix), code exploration (use code-explore). Output: classified analysis + verdict…

sd0xdev/sd0x-harness · 73 tokens

code-explore

Pure Claude code investigation. Use when: tracing execution paths, understanding architecture, diagnosing issues. Not for: dual-perspective review (use code-investigate), code review (use codex-code-review). Output: analysis report with findings.

sd0xdev/sd0x-harness · 51 tokens

debug

Interactive debugging workflow with hypothesis-driven probe loop. Use when: unknown bugs, script errors, silent failures, troubleshooting. Not for: known bugs (use bug-fix), GitHub issue analysis (use issue-analyze), code understanding (use code-explore). Output: debug report with probe journal + root cause + fix.

sd0xdev/sd0x-harness · 67 tokens

code-investigate

Dual-perspective code investigation. Use when: deep code analysis needing both Claude and Codex perspectives. Not for: quick exploration (use code-explore), code review (use codex-code-review). Output: integrated findings from dual analysis.

sd0xdev/sd0x-harness · 52 tokens

git-investigate

Git history investigation. Use when: tracking code changes, finding where bugs were introduced, root cause analysis. Not for: code exploration (use code-explore), issue analysis (use issue-analyze). Output: history trace + root cause report.

sd0xdev/sd0x-harness · 53 tokens

simplify

Wrap-up refactoring — simplify code, eliminate duplication, preserve behavior.

sd0xdev/sd0x-harness · 16 tokens