mockserver-monorepo: Skill for OpenCode

.opencode/skills/pr-review/SKILL.md

pr-review is a skill for OpenCode from mock-server/mockserver-monorepo. It costs 74 tokens per session (2,044 once invoked), scanned A, original, Apache-2.0.

A report generator that reviews every open pull request in the MockServer GitHub repository and classifies its status.

In plain words
What is it for?
Use it to check the repository's open pull requests and produce a report of which can merge, need changes, are stale, or duplicate other work.
Why use it?
It gathers mergeability, outdated changes, needed work, and duplicate information in one structured review, provided GitHub access is available.

Skill for OpenCode

Written for OpenCode: installed under .opencode/.

This is mock-server/mockserver-monorepo's own configuration. It tells OpenCode how to work on mockserver-monorepo itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything mockserver-monorepo configures →

About the project

MockServer is a testing server and proxy that imitates APIs, records and changes network traffic, and deliberately introduces failures. It is for developers testing applications against unavailable dependencies, debugging requests, and checking how systems handle degraded services across several network protocols. The catalogue add-ons help operate, configure, and test MockServer.

mock-server/mockserver-monorepo · 4,967 stars · on GitHub · mock-server.com

Reuse

Borrowing it

Nothing to install: this file belongs to mock-server/mockserver-monorepo. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/mock-server/mockserver-monorepo/master/.opencode/skills/pr-review/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/mock-server/mockserver-monorepo

Made for: OpenCode.

Wrote 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.

agentmods badge for pr-review

README.md
[![agentmods](https://agentmods.dev/badge/skills/mock-server/mockserver-monorepo/pr-review/github.svg)](https://agentmods.dev/skills/mock-server/mockserver-monorepo/pr-review)
Your own site
<a href="https://agentmods.dev/skills/mock-server/mockserver-monorepo/pr-review"><img src="https://agentmods.dev/badge/skills/mock-server/mockserver-monorepo/pr-review/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.

agentmods 80×15 button for pr-review

Your own site · 80×15
<a href="https://agentmods.dev/skills/mock-server/mockserver-monorepo/pr-review"><img src="https://agentmods.dev/badge/skills/mock-server/mockserver-monorepo/pr-review.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 74 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,044 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 1 finding. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector warn 7 Sept 2026
SkillSpector: 9 findings, up to high

These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →

  • high Privilege Escalation · line 18
    Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
    Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
  • medium Data Exfiltration · line 39
    Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
    Fix: Verify the destination URL is trusted and necessary. Remove or replace with documented APIs. Ensure no secrets, tokens, or PII are transmitted.
  • medium Data Exfiltration · line 49
    Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
    Fix: Verify the destination URL is trusted and necessary. Remove or replace with documented APIs. Ensure no secrets, tokens, or PII are transmitted.
  • medium Data Exfiltration · line 80
    Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
    Fix: Verify the destination URL is trusted and necessary. Remove or replace with documented APIs. Ensure no secrets, tokens, or PII are transmitted.
  • medium Data Exfiltration · line 88
    Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
    Fix: Verify the destination URL is trusted and necessary. Remove or replace with documented APIs. Ensure no secrets, tokens, or PII are transmitted.
  • medium Data Exfiltration · line 96
    Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
    Fix: Verify the destination URL is trusted and necessary. Remove or replace with documented APIs. Ensure no secrets, tokens, or PII are transmitted.
  • medium Data Exfiltration · line 104
    Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
    Fix: Verify the destination URL is trusted and necessary. Remove or replace with documented APIs. Ensure no secrets, tokens, or PII are transmitted.
  • medium Data Exfiltration · line 116
    Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
    Fix: Verify the destination URL is trusted and necessary. Remove or replace with documented APIs. Ensure no secrets, tokens, or PII are transmitted.
  • medium Data Exfiltration · line 164
    Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
    Fix: Verify the destination URL is trusted and necessary. Remove or replace with documented APIs. Ensure no secrets, tokens, or PII are transmitted.
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00074 $0.02044
Opus 5 $0.00037 $0.01022
Sonnet 5 $0.00015 $0.00409
Haiku 4.5 $0.00007 $0.00204

Measured 9d ago against content hash 1095441ffe9a, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

pr-review scanned grade A with 1 finding 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 9d 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.

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

curl -sH "Authorization: token $GITHUB_TOKEN" \
.opencode/skills/pr-review/SKILL.md · 243 lines

How it starts

The opening of the file, as written. The whole thing — 243 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Pull Request Review Report

Analyze all open pull requests on the MockServer GitHub repository and produce a comprehensive report covering mergeability, staleness, actionability, and duplicates.

Prerequisites

  • GITHUB_TOKEN environment variable set with a GitHub personal access token that has repo scope for github.com, OR
  • gh CLI authenticated to github.com (gh auth login --hostname github.com)

Check which is available:

if [ -n "$GITHUB_TOKEN" ]; then
  echo "Using GITHUB_TOKEN"
elif gh auth status --hostname github.com 2>/dev/null; then
  echo "Using gh CLI"
else
  echo "ERROR: Set GITHUB_TOKEN or run: gh auth login --hostname github.com"
  exit 1
fi

Repository

  • Owner: mock-server
  • Repo: mockserver
  • API Base: https://api.github.com/repos/mock-server/mockserver-monorepo

Step 1: Fetch All Open PRs

Fetch all open PRs with full metadata. Paginate if there are more than 100:

# Using GITHUB_TOKEN
curl -sH "Authorization: token $GITHUB_TOKEN" \
  -H "Accept: application/vnd.github.v3+json" \
  "https://api.github.com/repos/mock-server/mockserver-monorepo/pulls?state=open&per_page=100&page=1" \
  | jq '[.[] | {
    number,
    title,
    user: .user.login,
    created_at,
    updated_at,
    head_ref: .head.ref,
    head_sha: .head.sha,
    base_ref: .base.ref,
    mergeable_state: .mergeable_state,
    draft: .draft,
    labels: [.labels[].name],
    body: (.body // "" | .[0:200])
  }]'
# Using gh CLI (if authenticated to github.com)
gh pr list --repo mock-server/mockserver-monorepo --state open --limit 100 \
  --json number,title,author,createdAt,updatedAt,headRefName,baseRefName,isDraft,labels,mergeable,reviewDecision

Step 2: Get Detailed PR Info

For each PR, fetch merge status and review details:

# Merge status (requires individual PR fetch for mergeable field)
curl -sH "Authorization: token $GITHUB_TOKEN" \
  -H "Accept: application/vnd.github.v3+json" \
  "https://api.github.com/repos/mock-server/mockserver-monorepo/pulls/{number}" \
  | jq '{number, mergeable, mergeable_state, rebaseable, maintainer_can_modify, changed_files, additions, deletions}'

Read the full file on GitHub · 243 lines

Changes

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.

  1. 9d ago First seen · 243 lines · 74 tokens per session scan A 1095441ffe9a

Subscribe to this mod's changes

pr-review is a skill published in the GitHub repository mock-server/mockserver-monorepo (4,967 stars, last pushed today), licensed Apache-2.0. It adds 74 tokens to every session and 2,044 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other skills, from other repositories

bmad-loop-resolve

Interactive escalation-resolution workflow for the bmad-loop orchestrator. A bmad-loop run paused on a CRITICAL escalation (a contradiction or gap a dev/review session could not safely resolve alone); you and the human disambiguate the frozen spec so the story can be re-driven. Invoked as /bmad-loop-resolve . Unlike…

mmornati/leanproxy-mcp · 97 tokens

bmad-review-edge-case-hunter

Walk every branching path and boundary condition in content, report only unhandled edge cases. Orthogonal to adversarial review - method-driven not attitude-driven. Use when you need exhaustive edge-case analysis of code, specs, or diffs.

mmornati/leanproxy-mcp · 55 tokens

bmad-loop

Iterate over a list of story keys, executing dev → review → PR → CI → merge for each. Use when the user says "loop these stories [list]" or "run the loop on [story keys]".

mmornati/leanproxy-mcp · 48 tokens

bmad-retrospective

Post-epic review to extract lessons and assess success. Use when the user says "run a retrospective" or "lets retro the epic [epic]".

mmornati/leanproxy-mcp · 38 tokens

bmad-editorial-review-structure

Structural editor that proposes cuts, reorganization, and simplification while preserving comprehension. Use when user requests structural review or editorial review of structure.

mmornati/leanproxy-mcp · 35 tokens

bmad-code-review

Review code changes adversarially using parallel review layers (Blind Hunter, Edge Case Hunter, Acceptance Auditor) with structured triage into actionable categories. Use when the user says "run code review" or "review this code".

mmornati/leanproxy-mcp · 50 tokens