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 tomzx/agents --skill handle-issue-commentgit clone --depth 1 https://github.com/tomzx/agentsWrote 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/tomzx/agents/handle-issue-comment)<a href="https://agentmods.dev/skills/tomzx/agents/handle-issue-comment"><img src="https://agentmods.dev/badge/skills/tomzx/agents/handle-issue-comment/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.
<a href="https://agentmods.dev/skills/tomzx/agents/handle-issue-comment"><img src="https://agentmods.dev/badge/skills/tomzx/agents/handle-issue-comment.svg" alt="Reviewed on agentmods" width="80" 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.00028 | $0.00605 |
| Opus 5.5 | $0.00011 | $0.00242 |
| Sonnet 5.5 | $0.00006 | $0.00121 |
| Haiku 4.5 | $0.00003 | $0.00060 |
Grade A, and why
handle-issue-comment 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 24d 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.
How it starts
The opening of the file, as written. The whole thing — 71 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Handle Issue Comment
Replies to a comment on a GitHub issue with a relevant response drawn from the codebase, issue description, and prior discussion.
Prerequisites
ghCLI authenticated with access to the target repository- Issue URL (
$1) pointing to an existing GitHub issue
Skill attribution (GitHub)
Before posting any issue comment with gh, read github-post-attribution/SKILL.md and append the Posted with footer for SKILL_DIR = handle-issue-comment.
Communication guidelines (outbound text)
Before composing any text posted or drafted on the user's behalf, apply communication-guidelines/SKILL.md.
Steps
- Fetch the issue and all its comments:
gh issue view $1 --comments - Clone the repository to gather codebase context:
gh repo clone <owner>/<repo> - Review the full comment thread to understand the discussion.
- Draft a reply that directly addresses the latest comment, grounded in codebase evidence and prior discussion.
- Post the reply (body = main reply plus Skill attribution footer):
gh issue comment $1 --body "..."
Example Usage
Scenario 1: Answering a technical question
/handle-issue-comment https://github.com/owner/repo/issues/20
Comment: "Where is the retry logic implemented?"
Action: Look up the codebase, find src/retry.py, post a reply pointing to the relevant file and lines.
Scenario 2: Confirming a bug is reproducible
/handle-issue-comment https://github.com/owner/repo/issues/45
Comment: "I can reproduce this on v2.3 but not v2.2." Action: Review the changelog and relevant code between those versions, post a reply with findings.
Scenario 3: Clarifying scope
/handle-issue-comment https://github.com/owner/repo/issues/77
Comment: "Should this also fix the related problem in the admin panel?" Action: Review the issue's acceptance criteria, reply stating whether the admin panel is in scope.
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.
- 24d ago Changed bd5243735694
- 27d ago Changed 212ff3a537af
- 28d ago Changed · +4 lines 21c307d79880
- 1mo ago First seen · 67 lines · 28 tokens per session scan A b9d9ce581ac0
handle-issue-comment is a skill published in the GitHub repository tomzx/agents (13 stars, last pushed yesterday), licensed MIT. It adds 28 tokens to every session and 605 once invoked, about $0.0001 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-09-03.
Other skills, from other repositories
autoreview
Structured code review through the shared OpenClaw agent-skills installation.
omh-code-review
This is an OMH code-review workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).
revdiff-plan
Review the last Codex assistant message (plan, analysis, or proposal) with inline annotations in a TUI overlay. Extracts the most recent response from Codex rollout files and opens it in revdiff for review and annotation. Activates on "revdiff-plan", "review plan with revdiff", "annotate plan", "review last response"…
explore-unknowns
Guide the user through a quadrant walk that maps the unknowns of a task — open by listing the known knowns, then work through known unknowns, unknown knowns, and unknown unknowns one stage at a time, ending with a complete four-quadrant map in the user's hands. Use when a request is ambiguous or underspecified, the…
re0-merge
Review and land an external contribution the way this suite does: gate it against the thesis, land it with the author's credit intact, complete a new skill rather than merging it raw, then approve, credit, and explain before closing. Use when reviewing a pull request, as any collaborator or maintainer, not only the…
asplos-writing-style
Use when drafting or revising ASPLOS prose — engineering the first two pages that rapid review actually reads, stating the cross-layer insight as one quotable sentence, structuring per-layer mechanism sections, writing bounded claims, and fitting everything into 11 self-contained pages that include figures and…