Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/sd0xdev/sd0x-harnessnpx agentmods add skills/sd0xdev/sd0x-harness/load-pr-reviewWrote 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/sd0xdev/sd0x-harness/load-pr-review)<a href="https://agentmods.dev/skills/sd0xdev/sd0x-harness/load-pr-review"><img src="https://agentmods.dev/badge/skills/sd0xdev/sd0x-harness/load-pr-review.svg" alt="Measured on agentmods" 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.00077 | $0.04368 |
| Opus 5 | $0.00039 | $0.02184 |
| Sonnet 5 | $0.00015 | $0.00874 |
| Haiku 4.5 | $0.00008 | $0.00437 |
Grade A, and why
load-pr-review 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 yesterday.
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 — 438 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Load PR Review
Trigger Keywords
load pr review, pr feedback, address review, review comments, pr comments
When NOT to Use
| Need | Use Instead |
|---|---|
| Create a code review | /codex-review-fast or /codex-review |
| Post new review comments | /pr-comment |
| Create a PR | /create-pr |
| PR status overview | /pr-summary |
| Investigate code history | /git-investigate |
Core Principle
Load review → independent per-thread triage → analysis report → user decides next step
Default: analysis-only. Fix and writeback require explicit --mode fix / --writeback.
Data plane (JS script) handles fetch/normalize/writeback.
Control plane (this SKILL.md) handles classification, fix orchestration, auto-loop.
Non-Negotiable Rules
| # | Rule | Violation = |
|---|---|---|
| 1 | Plan/fix mode MUST invoke /seek-verdict via Skill tool per unresolved thread (unless --no-verdict) |
Report invalid — re-run with verdict |
| 2 | Step 3 (Present) is blocked until Step 2 (Verdict Triage) completes | Report invalid |
| 3 | Each /seek-verdict must use fresh Codex context per thread (no batch) |
Triage invalid |
| 4 | Plan output MUST include Codex Verdict Threads field (non-empty, from Step 2) | Report rejected |
Analysis-Only Default ⚠️
This skill is an analysis tool by default. It loads PR review comments and produces a triage report. It does NOT auto-fix.
Prohibited Behaviors
| ❌ Prohibited | ✅ Correct |
|---|---|
| Auto-fixing code after loading PR reviews | Present analysis report, wait for user to invoke --mode fix |
| Editing files in plan mode | Only read and classify; no writes |
Suggesting "let me fix this" without explicit --mode fix |
"Use --mode fix to start fixing ACTIONABLE threads." |
| Skipping triage and jumping to fixes | Always complete Step 2 verdict triage before any action |
Skipping /seek-verdict and classifying threads with AI judgment alone |
Invoke /seek-verdict per thread via Skill tool; AI judgment is fallback only for failed calls |
Outputting plan table without Codex verdict data when --no-verdict was not passed |
Complete Step 2 before Step 3 |
What ships with it
5 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- yesterday Changed 1ceeccd5dfb6
- 3d ago First seen · 438 lines · 77 tokens per session scan A ac240f976fb4
load-pr-review is a skill published in the GitHub repository sd0xdev/sd0x-harness (188 stars, last pushed yesterday), licensed MIT. It adds 77 tokens to every session and 4,368 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-09-03.
Other skills, from other repositories
code-review
Two-mode skill: (1) adversarial review — spec compliance + code quality + security, confidence-scored findings with file:line evidence; (2) receiving review — verify-before- agreeing discipline for acting on external/human review feedback.
codebase-hygiene
Two-mode skill: (1) find semantic duplicates — functions doing the same thing under different names, invisible to copy-paste detectors; (2) deepen shallow modules — thin wrappers and pass-through layers that spread complexity. Advisory and read-only; changes route through BUILD with full gates.
evaluator-review-contract
Internal Auto-Harness evaluator skill for sprint contract review before implementation. Use only inside the Evaluator subagent during review mode.
comet-verify
Comet Phase 4: Verify and Close. Invoke with /comet-verify. Verify implementation matches design, handle development branch.
comet-review
A read-only review guide for checking the current Comet change, a managed software-change workflow. It focuses on correctness, security, and boundary problems without changing files or advancing the workflow.
comet-github-pr-review
A read-only review process for pull requests in Comet's GitHub repositories. A pull request is a proposed code change; the review checks its current code, related issue, comments, merge status, and automated checks.