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 J-StaR-Films-Studios/VibeCode-Protocol-Suite --skill pr-comment-fixgit clone --depth 1 https://github.com/J-StaR-Films-Studios/VibeCode-Protocol-SuiteWrote 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/j-star-films-studios/vibecode-protocol-suite/pr-comment-fix)<a href="https://agentmods.dev/skills/j-star-films-studios/vibecode-protocol-suite/pr-comment-fix"><img src="https://agentmods.dev/badge/skills/j-star-films-studios/vibecode-protocol-suite/pr-comment-fix/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/j-star-films-studios/vibecode-protocol-suite/pr-comment-fix"><img src="https://agentmods.dev/badge/skills/j-star-films-studios/vibecode-protocol-suite/pr-comment-fix.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.00093 | $0.01570 |
| Opus 5 | $0.00046 | $0.00785 |
| Sonnet 5 | $0.00019 | $0.00314 |
| Haiku 4.5 | $0.00009 | $0.00157 |
Grade A, and why
pr-comment-fix 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 5d 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 — 183 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PR Comment Fix Workflow
Checkout a PR branch, fetch unresolved review comments, fix each one, commit, reply, resolve, and push — all in one pass.
Prerequisites
Before starting, verify gh is authenticated:
gh auth status
If it fails, stop and tell the user to run gh auth login.
Step 1: Identify the PR
Determine the target PR from the user's message. They might give you a PR number (#142), a branch name (feature/new-parser), or a URL. Normalize to a PR number early:
# If given a branch name, find its open PR
gh pr list --head <branch-name> --state open --json number --jq '.[0].number'
Once you have the PR number, fetch the branch name and check it out:
gh pr checkout <pr-number>
This ensures you're on the exact branch the PR tracks — not a stale local copy.
Step 2: Fetch unresolved review comments
Pull all review comments and filter to unresolved threads. Each comment has a thread ID, file path, line number, and body.
gh api graphql -f query='
query($owner: String!, $repo: String!, $pr: Int!) {
repository(owner: $owner, name: $repo) {
pullRequest(number: $pr) {
reviewThreads(first: 100) {
nodes {
id
isResolved
comments(first: 10) {
nodes {
body
path
line
author { login }
}
}
}
}
}
}
}
' -f owner='{owner}' -f repo='{repo}' -F pr=<pr-number>
Extract {owner} and {repo} from the current git remote:
gh repo view --json owner,name --jq '"\(.owner.login) \(.name)"'
Filter to threads where isResolved is false. If every thread is already resolved, tell the user there's nothing to fix and stop.
Step 3: Triage comments
Not every comment is actionable code feedback. Classify each unresolved thread:
- Actionable — requests a concrete code change (rename, refactor, fix bug, add validation, change logic, etc.)
- Question / Discussion — asks "why did you do X?" or debates an approach with no clear fix directive
- Nit / Style — trivial formatting or naming preferences
- Praise / Acknowledgement — compliments, thumbs-up, "looks good"
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.
- 5d ago First seen · 183 lines · 93 tokens per session scan A 8cd3976399e6
pr-comment-fix is a skill published in the GitHub repository J-StaR-Films-Studios/VibeCode-Protocol-Suite (24 stars, last pushed 4d ago), licensed ISC. It adds 93 tokens to every session and 1,570 once invoked, about $0.0005 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-09-03.
Other skills, from other repositories
pr-review
Intent-aware map-reduce PR review with CI/CD support, confidence gating, and intelligent comment deduplication.
pr-walkthrough
Generate an evidence-grounded markdown walkthrough for a pull request.
address-pr-feedback
Unified PR feedback workflow - collect, triage, and fix review comments in a single command.
pr-splitter
Analyse an oversized pull request or proposed branch changeset and decompose it into smaller, dependency-aware, independently reviewable pull requests. Use when a PR is too large for effective review or when the user asks to split, stack, or repackage a feature branch without changing its final behaviour. Do not use…
git-review
Review code changes against requirements and original design. Validates implementation correctness, design alignment, code quality, and runs tests. Use before committing or creating a PR.
comprehensive-review-pr-enhance
You are a PR optimization expert specializing in creating high-quality pull requests that facilitate efficient code reviews. Generate comprehensive PR descriptions, automate review processes, and ensure PRs follow best practices for clarity, size, and reviewability.