Borrowing it
Nothing to install: this file belongs to AntaresQAQ/VoxMesh. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/AntaresQAQ/VoxMesh/main/.github/skills/pr-review-autopilot/SKILL.mdgit clone --depth 1 https://github.com/AntaresQAQ/VoxMeshWrote 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/antaresqaq/voxmesh/pr-review-autopilot)<a href="https://agentmods.dev/skills/antaresqaq/voxmesh/pr-review-autopilot"><img src="https://agentmods.dev/badge/skills/antaresqaq/voxmesh/pr-review-autopilot/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/antaresqaq/voxmesh/pr-review-autopilot"><img src="https://agentmods.dev/badge/skills/antaresqaq/voxmesh/pr-review-autopilot.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.00079 | $0.02292 |
| Opus 5 | $0.00039 | $0.01146 |
| Sonnet 5 | $0.00016 | $0.00458 |
| Haiku 4.5 | $0.00008 | $0.00229 |
Grade A, and why
pr-review-autopilot 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 10d 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 — 324 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PR Review Autopilot
Own one pull request from review through merge for this repository. Continue looping until the current PR head has completed CI and GitHub Copilot review, no unresolved or new actionable comments remain, and the PR is merged.
Authorization
Use this skill only when the user has explicitly authorized each of these operations for the specified PR:
- edit the PR branch
- run tests, builds, lint, type checks, and E2E checks
- create focused commits
- push the branch
- reply to and resolve review threads
- wait for repeated GitHub Copilot reviews
- merge the PR after the stable-clean gate passes
Naming this skill alone does not override repository rules that require operation-specific confirmation. The invocation must explicitly authorize commit, push, and merge for this PR. Otherwise, do not use this skill and do not infer authorization.
Do not amend, rebase, force-push, or merge a different PR. Follow repository instructions and any stricter current-session rules. Include repository- or session-required commit trailers.
Inputs
Determine from the user request or current branch:
- repository owner/name
- pull request number
- PR head branch and SHA
- base branch
- repository validation command
- repository merge method
If the PR is not explicit, resolve it from the current branch with gh pr view. Stop only if multiple PRs are genuinely ambiguous.
Core Invariants
- Never claim completion while a review or required check for the current head is pending.
- Never merge with an unresolved review thread, failing required check, conflict, draft state, or blocking review decision.
- Never treat an old clean review as valid after pushing a new commit. The clean review must cover the current head SHA.
- Inspect review summaries as well as published threads. GitHub Copilot may place useful findings under Suppressed comments without creating a thread.
- Fix valid findings at the root cause. For incorrect, stale, or conflicting findings, reply with concrete evidence before resolving.
- Preserve user changes and keep fixes scoped to the PR.
- Use targeted validation while iterating and the repository's full required validation before each final push intended for merge.
- A successful workflow/check run is not proof that no comments were added. Always fetch reviews and threads after the Copilot review job completes.
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.
- 10d ago First seen · 324 lines · 79 tokens per session scan A 277986fd305e
pr-review-autopilot is a skill published in the GitHub repository AntaresQAQ/VoxMesh (1 stars, last pushed today), licensed MIT. It adds 79 tokens to every session and 2,292 once invoked, about $0.0004 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…
oss-maintainer
Run an open-source project's issue/PR/release loop like a careful human maintainer — triage to root cause, absorb community PRs before duplicating them, gate every merge, ship honest releases, and thank the people doing your QA for free.