agentmods.dev

checkcomments

checkcomments is a skill for Claude Code from LuisFelipeMoro/Harness-devkit. It costs 87 tokens per session (445 once invoked), scanned A, original, MIT.

A read-only tool that lists every unresolved comment on the current branch's GitHub pull request, grouped by file and line. A pull request is a proposed code change submitted for review.

In plain words
What is it for?
Use it to inspect open pull-request comments, including inline notes and general discussion, when an authenticated GitHub CLI is available.
Why use it?
It collects review feedback in one report without replying to comments, resolving them, or changing the code.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

Part of the pr-workflow plugin — 2 skills shipped together

not rated 13repo changed 1mo ago A scan 87 tokens original MIT

Good fit Use it to inspect open pull-request comments, including inline notes and general discussion, when an authenticated GitHub CLI is available.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/luisfelipemoro/harness-devkit/checkcomments
View source ↗ LuisFelipeMoro/Harness-devkit
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 LuisFelipeMoro/Harness-devkit --skill checkcomments
Clone the repo
git clone --depth 1 https://github.com/LuisFelipeMoro/Harness-devkit

Made for: Claude Code.

Or install pr-workflow, the plugin that ships this one along with the rest of its 2 skills.

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 checkcomments

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/luisfelipemoro/harness-devkit/checkcomments"><img src="https://agentmods.dev/badge/skills/luisfelipemoro/harness-devkit/checkcomments.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 87 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 445 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.
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.00087 $0.00445
Opus 5.5 $0.00035 $0.00178
Sonnet 5.5 $0.00017 $0.00089
Haiku 4.5 $0.00009 $0.00044

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

Security

Grade A, and why

checkcomments 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 1mo 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.

plugins/pr-workflow/skills/checkcomments/SKILL.md · 34 lines

What it actually says

checkcomments

List all open comments on the current branch's PR, grouped by file. No actions taken, no files modified.

Contract

Inputs: the current git branch (used to resolve the open PR); a repo with gh authenticated. Outputs: a printed report — the PR URL, inline comments grouped by file and sorted by line, then general PR comments. No files written, no API mutations. Boundary: does NOT reply to, resolve, or create comments; does NOT modify code, branches, or the PR.

Dependencies (verify before starting):

  • gh — GitHub CLI, authenticated; used to resolve the PR and read comments via gh api.
  • git — to read the current branch name.

Steps

  1. Verify prerequisites — gh auth status; stop if not authenticated.
  2. Get the current branch (git branch --show-current); stop if detached HEAD.
  3. Find the open PR for that branch; stop if none — report "No open PR found".
  4. Resolve OWNER and REPO.
  5. Fetch inline review comments (pulls/.../comments).
  6. Fetch general PR comments (issues/.../comments).
  7. Display: PR URL, inline comments grouped by file and sorted by line, then general comments.

Exact commands, API field handling, alignment rules, and the output example: references/procedure.md.

Done when: the PR URL and both comment sections are printed (each section shows its "No … comments." line when empty). If no open PR resolves for the branch, stop and report that instead of printing an empty report.

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. 1mo ago Changed · +29 tokens per session fa925a3a6e6c
  2. 1mo ago First seen · 34 lines · 58 tokens per session scan A 3599d8c17750

Subscribe to this mod's changes

checkcomments is a skill published in the GitHub repository LuisFelipeMoro/Harness-devkit (13 stars, last pushed today), licensed MIT. It adds 87 tokens to every session and 445 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-31.

Code review
Related

Other skills, from other repositories

autoreview

Structured code review through the shared OpenClaw agent-skills installation.

openclaw/clawhub · 17 tokens

omh-code-review

This is an OMH code-review workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).

rlaope/oh-my-hermes · 48 tokens

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"…

umputun/revdiff · 84 tokens

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…

brycewang-stanford/Awesome-Journal-Skills · 65 tokens

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…

dzhng/skills · 162 tokens

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…

LilMGenius/paperthin · 70 tokens