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/.claude/commands/pipeline-investigation.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/commands/mock-server/mockserver-monorepo/pipeline-investigation)<a href="https://agentmods.dev/commands/mock-server/mockserver-monorepo/pipeline-investigation"><img src="https://agentmods.dev/badge/commands/mock-server/mockserver-monorepo/pipeline-investigation/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/commands/mock-server/mockserver-monorepo/pipeline-investigation"><img src="https://agentmods.dev/badge/commands/mock-server/mockserver-monorepo/pipeline-investigation.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00010 | $0.00070 |
| Opus 5 | $0.00005 | $0.00035 |
| Sonnet 5 | $0.00002 | $0.00014 |
| Haiku 4.5 | $0.00001 | $0.00007 |
Grade A, and why
pipeline-investigation 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 10d 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.
What it actually says
Use the Agent tool to spawn a pipeline-investigator subagent to investigate pipeline failures for the following request:
$ARGUMENTS
The pipeline-investigator agent should read .opencode/skills/pipeline-investigation/SKILL.md and follow its investigation workflow.
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.
- 10d ago First seen · 9 lines · 10 tokens per session scan A f6182932979e
pipeline-investigation is a command published in the GitHub repository mock-server/mockserver-monorepo (4,968 stars, last pushed yesterday), licensed Apache-2.0. It adds 10 tokens to every session and 70 once invoked, about $0.0001 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 commands, from other repositories
ci-debug
Diagnose a failing CI run against an 11-pattern playbook. Classifies the failure, cites the relevant memory entry, proposes the exact fix command — but NEVER applies without explicit user approval. Use when a specific PR check or GitHub Actions run failed and you want a diagnosis instead of speculation. Don't use for…
metrics
Apply the CLI runtime and safety contract before executing a command. Runtime --help is authoritative.
traces
Apply the CLI runtime and safety contract before executing a command. Runtime --help is authoritative.
add-debug-wait
Add a wait step to a CI workflow for debugging test failures.
pr-quality-gate-reliability
You are reviewing a pull request for production survivability: how the change behaves when its dependencies misbehave, time out, or fail.
drift-alert-issue
Detection Date: $DETECTIONDATE Workflow Run: $SERVERURL/$REPOSITORY/actions/runs/$RUNID.