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 charlieviettq/awesome-agent-skill --skill github-comment-triagegit clone --depth 1 https://github.com/charlieviettq/awesome-agent-skillWrote 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/charlieviettq/awesome-agent-skill/github-comment-triage)<a href="https://agentmods.dev/skills/charlieviettq/awesome-agent-skill/github-comment-triage"><img src="https://agentmods.dev/badge/skills/charlieviettq/awesome-agent-skill/github-comment-triage.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.00043 | $0.00320 |
| Opus 5 | $0.00022 | $0.00160 |
| Sonnet 5 | $0.00009 | $0.00064 |
| Haiku 4.5 | $0.00004 | $0.00032 |
Grade A, and why
github-comment-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 5d 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
GitHub comment triage
Workflow
- Collect all open review threads and inline comments (not just summary).
- Classify each item:
- Must fix — correctness, security, contract break, CI
- Should fix — clarity, maintainability, agreed convention
- Discuss — ambiguous or product decision
- Defer — out of scope; needs follow-up issue
- Order must-fix first, then should-fix, then discuss.
- Implement with minimal scoped changes; one logical commit per theme when possible.
- Reply on each thread: what changed, where, or why deferred (link issue if deferred).
- Re-verify tests/lint before requesting re-review.
Response patterns
Fixed in abc123 — [brief what changed]
Deferred: tracked in #NNN — [reason and scope boundary]
Anti-patterns
- Bulk "fixed" without pointing to commits or files.
- Ignoring nitpicks that hide real bugs.
- Expanding scope to unrelated refactors during comment sweep.
Output
Checklist table: comment | action | status | note.
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.
- 5d ago First seen · 41 lines · 43 tokens per session scan A 4ee4f12df403
github-comment-triage is a skill published in the GitHub repository charlieviettq/awesome-agent-skill (25 stars, last pushed 1mo ago), licensed MIT. It adds 43 tokens to every session and 320 once invoked, about $0.0002 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-09-03.
Other skills, from other repositories
pr-review
Address feedback left on a GitHub pull request: fetch unresolved review threads, make agreed Elixir/Phoenix code fixes, reply, and resolve. Use for a PR URL/number or reviewer comments. NOT for pre-PR review, findings triage, or CI monitoring.
phx-pr-review
Address feedback left on a GitHub pull request: fetch unresolved review threads, make agreed Elixir/Phoenix code fixes, reply, and resolve. Use for a PR URL/number or reviewer comments. NOT for pre-PR review, findings triage, or CI monitoring.
address-pr-feedback
Comprehensively addresses PR feedback by fetching all comments, deploying parallel agents for critical analysis of each suggestion, making implementation decisions, then systematically implementing fixes with incremental commits and browser validation. Use when you need to systematically process and implement all PR…
address-pr-comments
Fetches unresolved PR comments, categorizes them (must-fix, suggestion, question, nit), proposes fixes or replies for each, and executes approved actions. Use when addressing PR review feedback or when someone requests changes on your PR.
create-pr
Create a well-structured, product-focused pull request.
github-maintainer
Use this when the user wants maintainer-grade judgment over a GitHub project queue. The goal is not just to list issues or pull requests; it is to decide what each item means, what evidence exists, what is risky, and what should happen next.