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.
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.
curl -O https://raw.githubusercontent.com/mock-server/mockserver-monorepo/master/.opencode/skills/issue-review/SKILL.mdgit clone --depth 1 https://github.com/mock-server/mockserver-monorepoWrote 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/mock-server/mockserver-monorepo/issue-review)<a href="https://agentmods.dev/skills/mock-server/mockserver-monorepo/issue-review"><img src="https://agentmods.dev/badge/skills/mock-server/mockserver-monorepo/issue-review.svg" alt="Measured on agentmods" 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.00106 | $0.04820 |
| Opus 5 | $0.00053 | $0.02410 |
| Sonnet 5 | $0.00021 | $0.00964 |
| Haiku 4.5 | $0.00011 | $0.00482 |
Grade A, and why
issue-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 8d 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 — 533 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub Issue Review and Resolution
Systematically review a GitHub issue to determine its validity, classify it, and take the appropriate action — whether that is improving documentation, fixing a bug, or closing as not-a-bug.
Prerequisites
ghCLI authenticated togithub.com(gh auth login --hostname github.com)
gh auth status --hostname github.com 2>/dev/null || echo "ERROR: run 'gh auth login --hostname github.com'"
Repository
- Owner:
mock-server - Repo:
mockserver
Step 1: Parse Input and Fetch Issue
Extract the issue number from the user's input (URL or number).
URL Pattern:
https://github.com/mock-server/mockserver-monorepo/issues/{number}
Fetch the full issue with comments:
gh issue view {number} --repo mock-server/mockserver-monorepo --json number,title,body,author,createdAt,updatedAt,state,labels,comments,assignees
Read the issue carefully. Extract:
- Reported behaviour: what the user says is happening
- Expected behaviour: what the user expected
- Steps to reproduce: how to trigger the issue
- Environment: MockServer version, Java version, OS, deployment method (Docker, JAR, WAR, Maven plugin)
- Configuration: any custom properties, expectations, or settings mentioned
- Error messages: exact error text, stack traces, or log output
- Attachments: links to logs, screenshots, or configuration files
If critical information is missing (no version, no reproduction steps, no error output), note this as a gap but continue investigation with what is available.
Step 2: Validate the Issue — Is This Still Relevant?
Before deep investigation, check if the issue is outdated:
2a: Check MockServer Version
# Current released version
gh release list --repo mock-server/mockserver-monorepo --limit 1 --json tagName,publishedAt
# Version from pom.xml (development version — target the project version, not parent/plugin)
grep -m1 'SNAPSHOT' mockserver/pom.xml | sed 's/.*<version>\(.*\)<\/version>.*/\1/'
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.
- 8d ago First seen · 533 lines · 106 tokens per session scan A 12864fc4bfcd
issue-review is a skill published in the GitHub repository mock-server/mockserver-monorepo (4,966 stars, last pushed today), licensed Apache-2.0. It adds 106 tokens to every session and 4,820 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-08-30.
Other skills, from other repositories
systemic-issue-triage
Trigger: new issue, bug report, triage, backlog, issue flood, community report, root cause, dead-end, blocked user. Attack issues by root class, never one-by-one; fixes must shrink the system, not grow it.
triage-issue
Intelligently triage bug reports and error messages by searching for duplicates in Jira and offering to create new issues or add comments to existing ones. When an agent needs to: (1) Triage a bug report or error message, (2) Check if an issue is a duplicate, (3) Find similar past issues, (4) Create a new bug ticket…
plano-observability-debugging
Improve Plano tracing and debugging workflows. Use for sampling strategy, span attributes, and trace query-based root-cause analysis.
browse-flows
Browse Power Automate environments and flows interactively. Use when the user wants to browse, list, or explore their flows and environments.
operating-cadence
Designs the rhythm an organization runs on — which reviews happen weekly, monthly and quarterly, what each one decides, who owns the numbers presented, and how a signal at the front line reaches the people who can act on it. Use this to set up a management operating system, fix a meeting calendar that produces no…
factory-triage
Triage a Factory work item's issue — trace history, understand architecture, diagnose root cause, then advance the stage.