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/build-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/build-monitor)<a href="https://agentmods.dev/skills/mock-server/mockserver-monorepo/build-monitor"><img src="https://agentmods.dev/badge/skills/mock-server/mockserver-monorepo/build-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/build-monitor"><img src="https://agentmods.dev/badge/skills/mock-server/mockserver-monorepo/build-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.00075 | $0.02985 |
| Opus 5 | $0.00037 | $0.01492 |
| Sonnet 5 | $0.00015 | $0.00597 |
| Haiku 4.5 | $0.00007 | $0.00298 |
Grade A, and why
build-monitor 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 13d 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.
/ `bk job log` commands. (Prefer these over `bk auth token` + `curl` to the REST How it starts
The opening of the file, as written. The whole thing — 339 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Buildkite Build Monitor
Continuously monitor the Buildkite pipeline, detect failures, investigate root causes, fix code issues, perform adversarial review, and push fixes — all in an automated loop.
Tooling — use scripts/ci/bk-pipeline-status.sh
Do NOT re-derive the build polling/parsing each time. Use the reusable
scripts/ci/bk-pipeline-status.sh, which wraps the reliable bk build list
/ bk job log commands. (Prefer these over bk auth token + curl to the REST
API and over the AWS Secrets Manager tokens: only the local bk CLI dependably
has both build-state and read_build_logs scope here, and it does not need an
AWS SSO session — see docs/infrastructure/ci-cd.md.)
# one-shot status of a build (by commit prefix, build number, or newest)
scripts/ci/bk-pipeline-status.sh -p mockserver-java -c <commitSha>
scripts/ci/bk-pipeline-status.sh -p mockserver-java -b <buildNumber>
# tail the failing job's log for investigation
scripts/ci/bk-pipeline-status.sh -p mockserver-java -b <buildNumber> --logs -n 80
# find the failure in the WHOLE log (the failure is usually NOT in the tail)
scripts/ci/bk-pipeline-status.sh -p mockserver-java -b <buildNumber> \
--grep 'Tests run: [0-9]+, Failures: [1-9]|<<< (FAILURE|ERROR)|BUILD FAILURE|There was a timeout|npm error'
# raw JSON of the matched build (for classifying exit_status / agent state)
scripts/ci/bk-pipeline-status.sh -p mockserver-java -b <buildNumber> --json
It prints build#<n> <commit> build=<state> <job>=<state> exit=<code> and exits
0 when the watched job passed, 2 when failed/broken/canceled, 3 on timeout.
For continuous watching, drive it with the agent Monitor tool in --watch
mode instead of an in-context polling loop — it emits one line per state change
and exits when terminal, so you are only re-invoked on a real change:
Monitor(command="scripts/ci/bk-pipeline-status.sh -p mockserver-java -c <commitSha> --watch")
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.
- 13d ago First seen · 339 lines · 75 tokens per session scan A 008c01e32fd2
build-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 75 tokens to every session and 2,985 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.
Other skills, from other repositories
plano-observability-debugging
Improve Plano tracing and debugging workflows. Use for sampling strategy, span attributes, and trace query-based root-cause analysis.
proxypin-capture-workflow
Operate a local ProxyPin workflow for iPhone or Android capture, MCP request analysis, authorized personal-data export, and Mock rule management. Use when the user mentions ProxyPin, mobile HTTPS capture, ProxyPin MCP, captured API discovery, HAR-like export, or ProxyPin Mock collections.
codex-reconnect-repair
Diagnose and safely repair Codex "Reconnecting... 1/5" through "5/5" loops in the CLI, desktop app, or IDE on macOS, Linux, and Windows. Use when a Codex turn stalls on repeated stream reconnects or only succeeds after HTTPS fallback; do not use for generic login, quota, model, or rate-limit errors.
nccl_culprit_victim
NCCL proxy wait decomposition — culprit (sendgpuwait) vs victim (recvwait).
bmad-quick-dev
Implements any user intent, requirement, story, bug fix or change request by producing clean working code artifacts that follow the project's existing architecture, patterns and conventions. Use when the user wants to build, fix, tweak, refactor, add or modify any code, component or feature.
proxyclawd-bridge
Monitor and control ProxyClawd MITM proxy for Claude Code. Inspect intercepted API requests, view conversation history, and send messages through the proxy.