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/pr-monitor/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/pr-monitor)<a href="https://agentmods.dev/skills/mock-server/mockserver-monorepo/pr-monitor"><img src="https://agentmods.dev/badge/skills/mock-server/mockserver-monorepo/pr-monitor/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/mock-server/mockserver-monorepo/pr-monitor"><img src="https://agentmods.dev/badge/skills/mock-server/mockserver-monorepo/pr-monitor.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.00069 | $0.01231 |
| Opus 5 | $0.00034 | $0.00616 |
| Sonnet 5 | $0.00014 | $0.00246 |
| Haiku 4.5 | $0.00007 | $0.00123 |
Grade A, and why
pr-monitor 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 12d 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 — 168 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PR Monitor & Auto-Merge Skill
Purpose
Monitors Dependabot and Snyk dependency upgrade PRs, automatically merging them when builds pass. Handles javax/jakarta compatibility validation and provides detailed status reporting.
When to Use
- After creating/updating dependency upgrade PRs
- When dependency PRs are failing and you've pushed fixes
- When user says "monitor PRs", "watch builds", "merge when passing"
- After fixing build issues for Dependabot/Snyk PRs
Prerequisites
- Repository must be a git repository with GitHub remote
ghCLI must be authenticated- PRs must exist on GitHub
- Working directory must be the repository root
Workflow
1. Identify PRs to Monitor
Get PRs from today or specific PR numbers:
# Get all PRs from today
gh pr list --json number,title,createdAt,author --jq '.[] | select(.createdAt | startswith("'$(date +%Y-%m-%d)'"))'
# Or use specific PR numbers provided by user
2. Check Current Status
For each PR, check:
- Build status (Buildkite, GitHub Actions)
- Java compatibility (if dependency upgrade)
- PR state (open, closed, merged)
Use the bundled pr-monitor.sh script (see Tool Usage below).
3. Handle Different States
PASSING builds:
- Merge immediately with
gh pr merge <number> --squash --auto - Report success to user
PENDING builds:
- Continue monitoring
- Report current status
FAILING builds:
- Check if failure is due to Java version incompatibility
- Report failure details to user
- Do NOT merge
CLOSED/MERGED:
- Skip and report status
- Remove from monitoring list
4. Monitor Loop
Poll every 2 minutes (120 seconds) for up to 2 hours:
- Check status of all pending PRs
- Merge any that have passed
- Report status changes
- Exit when all PRs are merged or closed
Tool Usage
Use the bundled pr-monitor.sh script:
.opencode/skills/pr-monitor/pr-monitor.sh <pr_numbers_or_'today'>
Examples:
# Monitor all PRs from today
.opencode/skills/pr-monitor/pr-monitor.sh today
# Monitor specific PRs
.opencode/skills/pr-monitor/pr-monitor.sh 2001 2005 2006
# One-time check (no loop)
.opencode/skills/pr-monitor/pr-monitor.sh --check-once 2001
What ships with it
1 file 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.
- 12d ago First seen · 168 lines · 69 tokens per session scan A 5413b73445c6
pr-monitor is a skill published in the GitHub repository mock-server/mockserver-monorepo (4,969 stars, last pushed today), licensed Apache-2.0. It adds 69 tokens to every session and 1,231 once invoked, about $0.0003 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
github-release-management
Comprehensive GitHub release orchestration with AI swarm coordination for automated versioning, testing, deployment, and rollback management.
deployment-patterns
Deployment workflows, CI/CD pipeline patterns, Docker containerization, health checks, rollback strategies, and production readiness checklists for web applications. Use when setting up deployment infrastructure or planning releases.
agent-github-modes
Agent skill for github-modes - invoke with $agent-github-modes.
baby-sit
Monitor a GitHub pull request until CI is green, diagnose failures, and rerun only evidence-backed flaky GitHub Actions jobs.
atmos-hooks
Atmos hooks: lifecycle events, hook kinds, command/store/git/security hooks, step/steps hooks, when: conditions, scoping and overrides, toolchain integration, --skip-hooks, and Atmos Pro/local output.
atmos-pro
Atmos Pro setup and workflows: settings.pro, GitHub OIDC, affected and inventory uploads, stack locks, pro commit, workflow dispatch, merge queues, and drift detection.