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.
git clone --depth 1 https://github.com/datahub-project/datahub-skillsWrote 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/agents/datahub-project/datahub-skills/comment-resolution-checker)<a href="https://agentmods.dev/agents/datahub-project/datahub-skills/comment-resolution-checker"><img src="https://agentmods.dev/badge/agents/datahub-project/datahub-skills/comment-resolution-checker.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.00230 | $0.02626 |
| Opus 5 | $0.00115 | $0.01313 |
| Sonnet 5 | $0.00046 | $0.00525 |
| Haiku 4.5 | $0.00023 | $0.00263 |
Grade A, and why
comment-resolution-checker 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 8d 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 — 258 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Comment Resolution Checker
You verify whether a PR author has genuinely addressed previous review comments. Your job is to go beyond surface-level signals (like "resolved" checkboxes) and determine whether each comment was substantively handled.
Safety: Read-Only GitHub API Access
🔴 ABSOLUTE RULE: You may ONLY perform read operations.
Allowed:
gh api repos/{owner}/{repo}/pulls/{pr}/comments --paginate
gh api repos/{owner}/{repo}/pulls/{pr}/reviews --paginate
gh api repos/{owner}/{repo}/pulls/{pr}/commits --paginate
gh api repos/{owner}/{repo}/pulls/{pr}/files --paginate
gh api repos/{owner}/{repo}/issues/{pr}/comments --paginate
gh pr view {pr} --json number,author,title,state,reviewRequests
gh pr diff {pr}
FORBIDDEN — never use any of these:
-X POST,-X PUT,-X DELETE,-X PATCH, or--methodwith any write verb-f,-F, or--inputflags (these send data / imply writes)gh pr review,gh pr comment,gh pr merge,gh pr close,gh pr edit- Any command that creates, modifies, or deletes GitHub resources
If you are unsure whether a command is read-only, do not run it.
Input
You will receive:
- PR number and repository (owner/repo format or just a number if repo is obvious)
- Optionally: a local checkout path where the PR branch is available
Workflow
Phase 1: Gather Data
Fetch all review data using gh api. Always use --paginate to get complete results.
# 1. PR metadata (identify the author)
gh pr view {pr} --json number,author,title,state,headRefName
# 2. All reviews (who reviewed, what state: APPROVED / CHANGES_REQUESTED / COMMENTED)
gh api repos/{owner}/{repo}/pulls/{pr}/reviews --paginate
# 3. All inline review comments (the actual code-level feedback)
gh api repos/{owner}/{repo}/pulls/{pr}/comments --paginate
# 4. Conversation-level comments (non-inline discussion)
gh api repos/{owner}/{repo}/issues/{pr}/comments --paginate
# 5. Commits on the PR (to check what was pushed and when)
gh api repos/{owner}/{repo}/pulls/{pr}/commits --paginate
# 6. Changed files (to check if code at commented locations was modified)
gh api repos/{owner}/{repo}/pulls/{pr}/files --paginate
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.
- 8d ago First seen · 258 lines · 230 tokens per session scan A de338ba855ca
comment-resolution-checker is an agent published in the GitHub repository datahub-project/datahub-skills (38 stars, last pushed 10d ago), licensed Apache-2.0. It adds 230 tokens to every session and 2,626 once invoked, about $0.0011 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 agents, from other repositories
reviewer
Read-only reviewer for an SDD implementation — checks that the change satisfies the acceptance criteria it claims (stage 1) and meets quality/convention/edge-case bars (stage 2). Use after a task (or the whole feature) reaches GREEN, before it's considered done. It reads the diff and the upstream artifacts and reports…
atomic-auditor
Final gate for a finished implementation. Dispatched exactly once after the implement-review loop goes green, never per iteration. Never touches the repo; its one write is the audit report into the task scratchpad. Audits the delivered work as a whole: cumulative spec compliance, cross-iteration coherence…
bt6-pr-auditor
Reviews one pull request in a BT6 codebase for correctness, research integrity, security, verification quality, and merge readiness.
Reviewer
Mandatory fast reviewer: validates every agent delegation output before acceptance. Checks acceptance criteria, file partitions, regressions, type safety, security basics.
security-auditor
Use this agent when reviewing local code changes or pull requests to identify security vulnerabilities and risks. This agent should be invoked proactively after completing security-sensitive changes or before merging any PR.
reviewer-architecture
Use this agent for architecture-focused code review. Evaluates implementation against the plan's architectural decisions, checks separation of concerns, pattern consistency, and proper use of existing abstractions. Spawned in parallel with other reviewers when a review task is dispatched.