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 cisco-open/ai-harness-toolkit --skill gh-pr-comment-resolutiongit clone --depth 1 https://github.com/cisco-open/ai-harness-toolkitWrote 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/cisco-open/ai-harness-toolkit/gh-pr-comment-resolution)<a href="https://agentmods.dev/skills/cisco-open/ai-harness-toolkit/gh-pr-comment-resolution"><img src="https://agentmods.dev/badge/skills/cisco-open/ai-harness-toolkit/gh-pr-comment-resolution/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/cisco-open/ai-harness-toolkit/gh-pr-comment-resolution"><img src="https://agentmods.dev/badge/skills/cisco-open/ai-harness-toolkit/gh-pr-comment-resolution.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00063 | $0.00569 |
| Opus 5 | $0.00032 | $0.00284 |
| Sonnet 5 | $0.00013 | $0.00114 |
| Haiku 4.5 | $0.00006 | $0.00057 |
Grade A, and why
gh-pr-comment-resolution 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 9d 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
GH PR Comment Resolution
Overview
Use gh CLI + GraphQL to find Copilot review comments, map them to files, and resolve threads once the code is fixed. Provide a deterministic workflow for fetching comments, fixing issues, and closing review threads.
Workflow
1) Identify the PR and review threads
- Get the PR number for the current branch:
gh pr view --json number,title,url,headRefName
- Fetch review threads (includes thread ids for resolving):
gh api graphql -f query='query($owner:String!,$repo:String!,$number:Int!){repository(owner:$owner, name:$repo){pullRequest(number:$number){reviewThreads(first:50){nodes{id,isResolved,comments(first:20){nodes{id,body,author{login},path,position}}}}}}}' -f owner='<OWNER>' -f repo='<REPO>' -F number=<PR_NUMBER>
- Optionally list classic review comments for easier scanning:
gh api repos/<OWNER>/<REPO>/pulls/<PR_NUMBER>/comments
2) Triage Copilot comments
- Filter by
author.login(e.g.,copilot-pull-request-reviewer[bot]). - Group comments by
pathand map to files in the workspace. - For each comment, decide: fix in code or mark as already addressed.
3) Apply fixes
- Make code changes in the referenced file(s).
- If the file is vendored or patched, update the patch script instead of the vendored file.
4) Resolve review threads
- Resolve each thread via GraphQL:
gh api graphql -f query='mutation($threadId:ID!){resolveReviewThread(input:{threadId:$threadId}){thread{id,isResolved}}}' -F threadId='<THREAD_ID>'
- If a comment was already addressed, reply with context (optional) and resolve the thread.
5) Report back
- Summarize the fixes and list any comments resolved as "already handled".
- Suggest tests if relevant.
Notes
- Prefer GraphQL for review thread resolution because REST review comments do not expose thread ids.
- If reviewThreads exceed 50, paginate with
reviewThreads(first:50, after: <cursor>).
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.
- 9d ago First seen · 65 lines · 63 tokens per session scan A 7ac37a81b85e
gh-pr-comment-resolution is a skill published in the GitHub repository cisco-open/ai-harness-toolkit (11 stars, last pushed 13d ago), licensed Apache-2.0. It adds 63 tokens to every session and 569 once invoked, about $0.0003 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-31.
Other skills, from other repositories
review-implement-phase
Implements triaged review actions, commits focused fixes, and posts Done plus resolves threads. Use when the user wants only the implementation phase of the review-framework workflow.
engram-branch-pr
PR creation workflow for Engram following the issue-first enforcement system. Trigger: When creating a pull request, opening a PR, or preparing changes for review.
verify-behavior
Verify or reproduce visible product behavior by driving the real UI with pi-computer-use's checked tools, requiring verified expect postconditions and durable state evidence for meaningful UI flows. Use when triage needs visual reproduction, implementation needs behavioral proof, review needs interactive confirmation…
github-contributor
End-to-end playbook for shipping high-quality pull requests to open-source projects you don't maintain — discovery, CONTRIBUTING compliance, PR-size check, minimal-diff implementation, PR description with AI-assisted disclosure, conflict resolution, and post-submission maintainer interaction. Use whenever creating…
revdiff
Review diffs, files, and documents with inline annotations in a TUI overlay, or answer questions about revdiff usage, configuration, themes, and keybindings. Opens revdiff in agterm/tmux/zellij/herdr/kitty/wezterm/cmux/ghostty/iterm2/emacs-vterm, captures annotations, and addresses them. Works in git, hg, and jj repos…
write-pr
Reference standards for writing pull request titles and descriptions in the tldraw repository, plus the pre-flight comment sweep over the diff. Use as supporting guidance when another skill or workflow needs PR content standards, not as the user-facing create/update PR workflow.