Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add cboone/agent-harness-plugins/plugin install monitor-prWrote 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/cboone/agent-harness-plugins/resolve-copilot-feedback)<a href="https://agentmods.dev/skills/cboone/agent-harness-plugins/resolve-copilot-feedback"><img src="https://agentmods.dev/badge/skills/cboone/agent-harness-plugins/resolve-copilot-feedback/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/cboone/agent-harness-plugins/resolve-copilot-feedback"><img src="https://agentmods.dev/badge/skills/cboone/agent-harness-plugins/resolve-copilot-feedback.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.00052 | $0.14615 |
| Opus 5.5 | $0.00021 | $0.05846 |
| Sonnet 5.5 | $0.00010 | $0.02923 |
| Haiku 4.5 | $0.00005 | $0.01461 |
Grade A, and why
resolve-copilot-feedback 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 3d 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 — 715 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Copilot Feedback Resolver
Process and resolve GitHub Copilot's automated PR review comments systematically.
PR Comments Prohibition (CRITICAL)
NEVER leave comments directly on GitHub PRs. This is strictly forbidden:
gh pr review --comment- FORBIDDENgh pr comment- FORBIDDEN (except the single required final workflow summary in step 9)- Any GraphQL mutation that creates new reviews or PR-level comments - FORBIDDEN
- Responding to human review comments - FORBIDDEN
This skill ONLY processes Copilot-authored feedback, whether it arrives as a review thread or as a finding in a Copilot review body. Never interact with threads created by human reviewers.
Permitted operations:
- Fetch unresolved Copilot threads using the script's
fetchcommand - Fetch Copilot review bodies using the script's
fetch-reviewscommand - Audit every Copilot item on the PR using the script's read-only
auditcommand - Read existing PR comments (never write them) to check for prior summaries
- Reply to EXISTING Copilot threads using the script's
replycommand - Resolve Copilot threads using the script's
resolvecommand - Reply and resolve in one step using the script's
reply-and-resolvecommand - Read the pull request body with
gh pr view --json body, and correct it in step 8 withgh pr edit --body-file. Editing the body is not a PR comment.
Single exception: Step 9 uses gh pr comment with --body-file to post one required final workflow summary after terminal workflow state once PR context exists. This is the ONLY permitted use of gh pr comment in this skill. The final summary is blocking: if it cannot be posted, the workflow is incomplete.
Script Setup
All Copilot reads and thread writes use a dedicated script that handles pagination, variable binding, and Copilot author filtering automatically.
The script ships with this plugin. Invoke it via bash followed by the quoted path:
bash "${CLAUDE_PLUGIN_ROOT}/scripts/resolve-copilot-threads" fetch OWNER REPO PR_NUMBER
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.
- 3d ago First seen · 715 lines · 52 tokens per session scan A 1f139d0f59ea
resolve-copilot-feedback is a skill published in the GitHub repository cboone/agent-harness-plugins (2 stars, last pushed yesterday), licensed MIT. It adds 52 tokens to every session and 14,615 once invoked, about $0.0002 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-10-13.
Other skills, from other repositories
review-preflight
Review tooling for a PR: review-preflight prints REVIEW.md's criteria and the PR's live gate state before a review; ci-triage maps a PR's failing checks to already-filed issues.
pr-triage
4-phase PR backlog management with audit, deep code review, validated comments, and optional worktree setup. Use when triaging pull requests, catching up on pending code reviews, or managing a backlog of open PRs. Args: 'all' to review all, PR numbers to focus (e.g. '42 57'), 'en'/'fr' for language, no arg = audit…
validate-changes
Evaluate staged changes using LLM-as-a-Judge before committing.
review-pr
Comprehensive PR review -- full branch diff against base, commit-by-commit analysis, breaking change detection, conventional commit verification.
pr-audit
Audit a specified PR or PR-ready branch for submission or post-revision readiness. Bind the exact base/head, review commits and net changes, run safe project checks and inspect applicable CI. An audit alone does not authorize fixes, history changes or publication.
git-review
Review code changes, pull requests, or merge requests for bugs, code quality, security, and maintainability. Use when asked to review a PR, MR, diff, or set of changes. Also handles GitHub PRs and GitLab MRs.