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 fmflurry/settings-opencode --skill get-pr-commentsgit clone --depth 1 https://github.com/fmflurry/settings-opencodeWrote 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/fmflurry/settings-opencode/get-pr-comments)<a href="https://agentmods.dev/skills/fmflurry/settings-opencode/get-pr-comments"><img src="https://agentmods.dev/badge/skills/fmflurry/settings-opencode/get-pr-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/fmflurry/settings-opencode/get-pr-comments"><img src="https://agentmods.dev/badge/skills/fmflurry/settings-opencode/get-pr-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.00022 | $0.00951 |
| Opus 5.5 | $0.00009 | $0.00380 |
| Sonnet 5.5 | $0.00004 | $0.00190 |
| Haiku 4.5 | $0.00002 | $0.00095 |
Grade A, and why
get-pr-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 13d 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 — 120 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Get PR comments
If the current project has .claude/skills/get-pr-comments/SKILL.md or .opencode/skills/get-pr-comments/SKILL.md, read it and its references/; project specifics override this generic version.
Trigger
Need a concise, actionable summary of feedback (review comments, discussions) on the active pull request.
Workflow
1. Resolve the PR
Extract PR metadata:
gh pr view --json number,url,title,reviewDecision,reviews,comments
2. Fetch Comments
Retrieve all PR comments (not just reviews):
gh api repos/{owner}/{repo}/pulls/{number}/comments --paginate
If you don't have {owner}/{repo} readily, derive it from git remote get-url origin.
3. Fetch Review Threads (GraphQL)
For deeper context (resolved vs. open threads, outdated status, thread structure), optionally use:
gh api graphql -f query='
query {
repository(owner: "<owner>", name: "<repo>") {
pullRequest(number: <number>) {
reviewThreads(first: 100) {
nodes {
isResolved
isOutdated
path
line
comments(first: 10) {
nodes {
author {
login
}
body
url
}
}
}
}
}
}
}
'
4. Filter and Group
Apply these filters:
- Skip resolved threads: Threads marked
isResolved: trueare closed; do not include in the action list unless they're newly resolved and relevant context. - Flag outdated comments: Comments on outdated code (lines changed after the comment was posted) are marked
isOutdated: true. Flag these but include them (the author may intend a re-review after changes). - Filter bots: Exclude comments from bot accounts (e.g.,
dependabot,github-actions[bot],renovate[bot]). These are usually automated and do not require human response.
5. Group by Severity
Organize feedback into these buckets:
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.
- 13d ago First seen · 120 lines · 22 tokens per session scan A a4ff25541cee
get-pr-comments is a skill published in the GitHub repository fmflurry/settings-opencode (171 stars, last pushed yesterday), licensed MIT. It adds 22 tokens to every session and 951 once invoked, about $0.0001 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-03.
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.
pr
Draft a PR body from OMC's paper trail — the smallest visual that proves the change, evidence consumed from the verify protocol (never re-collected), reversibility from the ADR test on the diff, glossary language throughout.
otto-pr-review-loop
Run Polly and OCR on a PR until all findings settle.
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
A step-by-step guide for contributing code, tests, documentation, or build changes to open-source projects you do not maintain. It explains how to prepare a pull request that follows the project’s rules and is easier for maintainers to review.