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 euxx/claude-skills-for-copilot --skill gh-address-commentsgit clone --depth 1 https://github.com/euxx/claude-skills-for-copilotWrote 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/euxx/claude-skills-for-copilot/gh-address-comments)<a href="https://agentmods.dev/skills/euxx/claude-skills-for-copilot/gh-address-comments"><img src="https://agentmods.dev/badge/skills/euxx/claude-skills-for-copilot/gh-address-comments/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/euxx/claude-skills-for-copilot/gh-address-comments"><img src="https://agentmods.dev/badge/skills/euxx/claude-skills-for-copilot/gh-address-comments.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.00037 | $0.00774 |
| Opus 5 | $0.00018 | $0.00387 |
| Sonnet 5 | $0.00007 | $0.00155 |
| Haiku 4.5 | $0.00004 | $0.00077 |
Grade A, and why
gh-address-comments 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 11d 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 — 100 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Address PR Review Comments
Fetch all review comments for the current branch's open PR, present a numbered summary, and apply fixes for the comments the user selects.
Prerequisites
Verify gh authentication before doing anything else:
gh auth status
If unauthenticated, ask the user to run gh auth login, then stop.
Workflow
1. Resolve the PR
# if the user specified a PR number or URL:
gh pr view <number-or-url> --json number,url,headRefName
# otherwise (current branch):
gh pr view --json number,url,headRefName
Extract owner and repo from the returned url field — PR URLs have the form https://github.com/<owner>/<repo>/pull/<number>, so split on / to get the 4th and 5th segments. These are the base (target) repository coordinates, and are reliable even for cross-fork PRs.
2. Fetch comments
Run the following to get all review threads (inline) and conversation comments:
gh api graphql -f query='
query($owner:String!, $repo:String!, $number:Int!) {
repository(owner:$owner, name:$repo) {
pullRequest(number:$number) {
number url title state
comments(first:100) {
nodes { id body author { login } createdAt }
}
reviews(first:100) {
nodes { id state body author { login } submittedAt }
}
reviewThreads(first:100) {
nodes {
id isResolved isOutdated path line
comments(first:100) {
nodes { id body author { login } createdAt }
}
}
}
}
}
}' -F owner=<owner> -F repo=<repo> -F number=<pr-number>
If GraphQL is unavailable, fall back to:
gh pr view <pr-number> -R <owner>/<repo> --json reviews,reviewRequests,comments
Note: the fallback output does not include thread-level isResolved/isOutdated fields. In fallback mode, treat all returned comments as actionable.
3. Present a numbered summary
List every unresolved comment/thread (or all comments in fallback mode) with a number, author, file/line (if inline), and a one-line description of the requested change. Example:
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.
- 11d ago First seen · 100 lines · 37 tokens per session scan A f40c32f6d48c
gh-address-comments is a skill published in the GitHub repository euxx/claude-skills-for-copilot (4 stars, last pushed 2mo ago), licensed MIT. It adds 37 tokens to every session and 774 once invoked, about $0.0002 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
pr-comment-review
Audit and remediate an open GitHub PR's review feedback: verify Copilot and Codex actually reviewed, drive every unresolved thread to a fix-or-justify reply, correct PR title/description drift against the real diff, and run a one-time self-review pass. Trigger on "have all PR comments been addressed", "did copilot and…
babysit
Watch a pull request or review cycle until it is ready to merge. Use when asked to babysit, monitor, or keep checking PR comments, reviews, and CI until all actionable issues are resolved.
code-review
Review the current diff, or a PR number/branch/path target, for correctness bugs and reuse/simplification/efficiency cleanups at the given effort level (low/medium: fewer, high-confidence findings; high→max: broader coverage, may include uncertain findings; ultra: deep multi-agent review in the cloud); with no level…
release-jetbrains
Use when releasing the Kilo JetBrains plugin -- resolve a version ("next rc" or explicit), run the prepare workflow, edit and commit a filtered human-readable changelog on the release PR, then watch publish to completion.
github
GitHub via gh CLI: PRs, issues, reviews, repos, auth.
kilocode-merge-minimizer
Use when changing shared upstream-owned files to add Kilo-specific behavior, editing kilocodechange markers in shared code, or moving additive behavior out of shared code to reduce upstream merge conflicts. Do not use for changes confined to Kilo-owned paths such as packages/kilo-vscode/ or packages/kilo-ui/.