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/ui-screenshots/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/ui-screenshots)<a href="https://agentmods.dev/skills/mock-server/mockserver-monorepo/ui-screenshots"><img src="https://agentmods.dev/badge/skills/mock-server/mockserver-monorepo/ui-screenshots.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 3 findings, up to medium
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 →
- medium MCP Rug Pull · line 24 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 95 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium Rogue Agent · line 86 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
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.00103 | $0.02614 |
| Opus 5 | $0.00051 | $0.01307 |
| Sonnet 5 | $0.00021 | $0.00523 |
| Haiku 4.5 | $0.00010 | $0.00261 |
Grade A, and why
ui-screenshots 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 — 213 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Regenerate Dashboard Documentation Screenshots
Refresh the website's dashboard screenshots after UI changes. The flow brings up
a fully-populated demo dashboard, then captures one crisp PNG per tab at the same
geometry as the existing images so they drop in with no <img> edits.
TL;DR
cd mockserver-ui
npm install # first time only — fetches playwright
npx playwright install chromium # first time only — fetches the browser binary
npm run screenshots:all # demo up → capture every tab → demo down
screenshots:all writes 19 PNGs straight into
jekyll-www.mock-server.com/images/ (the live website paths). Review the diff,
then commit the changed images.
How it works
screenshots:all runs the demo in two phases, because load injection and the
screenshots want opposite things (see "Why two phases" below):
flowchart TB
subgraph P1["Phase 1 — content tabs"]
A1["demo --with-broker\n(NO load injection)"] --> A2["capture 17 content tabs\n(Traffic, Sessions, Mocks, Chaos, …)"]
end
subgraph P2["Phase 2 — chart tabs"]
B1["demo --with-broker --with-load-injection"] --> B2["warm up ~90s"] --> B3["capture Metrics + Performance"]
end
P1 --> P2 --> C["MockServer<Tab>.png → jekyll-www.../images/"]
Each phase: background npm run demo, wait for the "Ready — populated demo
environment" line, run the Playwright capture, tear the demo down (trap EXIT).
Two scripts, both in mockserver-ui/scripts/:
| Script | Role |
|---|---|
capture-docs-screenshots.sh |
Orchestrator — runs both demo phases, captures, tears down. npm run screenshots:all. |
capture-dashboard-screenshots.mjs |
The Playwright capture — assumes the dashboard is already running, waits for the WebSocket to show "Connected", navigates each tab, drives it into a rich state, shoots. npm run screenshots. |
Curated tab states
The capture doesn't just navigate — for several tabs it drives a richer
documentation state (each is a best-effort prepare step in the .mjs; a
failure is logged and the shot still happens):
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 · 213 lines · 103 tokens per session scan A ab6942297697
ui-screenshots is a skill published in the GitHub repository mock-server/mockserver-monorepo (4,966 stars, last pushed today), licensed Apache-2.0. It adds 103 tokens to every session and 2,614 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
aluvia
Use Aluvia when a cloud agent is in the wrong country for a site; when a page says not available in your region, this content is not available in your country, we don’t ship to your location, or other geo-restriction; when you need the browser to use an IP in a specific country (aluvia proxy-on --geo US; run aluvia…
kaido-proxy-integration
Integrate Kaido (Caido) proxy with Claude Code CLI for automated HTTP interception, request replay, and vulnerability scanning. Based on Critical Thinking Ep. 166.
browser-stealth
Browser automation stealth and residential proxy routing — patchright anti-detection, Playwright proxy at correct context level, sticky residential sessions, navigator.webdriver masking, datacenter vs residential IP fingerprinting, and page.evaluate fetch fallback.
burp-suite-advanced-methodology
Master Burp Suite Professional for comprehensive web application security testing. Use this skill when performing manual web application assessments with Burp Suite including proxy interception, Scanner automation, Intruder attacks, Repeater analysis, and extension integration. Covers advanced techniques like…
novada-proxy
Residential proxy tools for AI agents — fetch, crawl, search, extract, render through 2M+ IPs. Bypass anti-bot, geo-target 195+ countries. Use when: scraping websites, researching topics, extracting structured data, or any task that needs web access through a proxy.
10router-web-fetch
Fetch URL → markdown / text / HTML via 10Router /v1/web/fetch using Firecrawl / Jina Reader / Tavily Extract / Exa Contents. Use when the user wants to scrape a webpage, extract URL content, read article, or convert a URL to markdown.