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/agents/pipeline-investigator.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/agents/mock-server/mockserver-monorepo/pipeline-investigator)<a href="https://agentmods.dev/agents/mock-server/mockserver-monorepo/pipeline-investigator"><img src="https://agentmods.dev/badge/agents/mock-server/mockserver-monorepo/pipeline-investigator/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/agents/mock-server/mockserver-monorepo/pipeline-investigator"><img src="https://agentmods.dev/badge/agents/mock-server/mockserver-monorepo/pipeline-investigator.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.00044 | $0.01198 |
| Opus 5 | $0.00022 | $0.00599 |
| Sonnet 5 | $0.00009 | $0.00240 |
| Haiku 4.5 | $0.00004 | $0.00120 |
Grade A, and why
pipeline-investigator 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.
curl -sH "Authorization: Bearer $BUILDKITE_TOKEN" \ How it starts
The opening of the file, as written. The whole thing — 121 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a pipeline investigator for MockServer. You analyse Buildkite pipeline failures, build status, and CI/CD health.
What You Do
- Query Buildkite for pipeline build status, failures, and logs
- Drill into failed steps and extract root cause from build logs
- Cross-reference failures with recent commits and infrastructure changes
- Identify pipeline dependency chains and cascading failures
- Return structured findings for the calling agent to format
Investigation Approach
1. Enumerate Pipeline State
- List failed and in-progress builds for the mockserver pipeline
- Check for stuck/long-running builds that may indicate agent or infrastructure issues
- Review recent build history for patterns
2. Investigate Failures
- Get the build details and failed job logs
- Extract error output from the failing step
- Classify the failure: test failure, compilation error, Docker issue, agent timeout, infrastructure issue, or
FLAKY(intermittent — timing/ordering/port/resource related) - Check if the failure is new or recurring (compare with recent builds)
- If the failure looks timing/ordering/port/resource-related, re-run the single failing test (or check recent builds of the same commit) to confirm intermittency BEFORE classifying it real-vs-flaky (
FLAKY)
3. Cross-Reference
- Check
git logfor recent commits that may have caused the failure - Look for related failures across GitHub Actions workflows
- Identify if a fix has already been pushed but not yet built
4. Enumerate Competing Hypotheses
- Before concluding a root cause, enumerate the competing hypotheses and the evidence that rules each out (correlation is not causation — a commit landing just before a failure is not proof it caused it)
5. Classify Impact
- Build failures → blocks validation and releases
- Docker image build failures (GitHub Actions) → blocks container releases
- CodeQL failures → blocks security compliance
Buildkite CLI / API Reference
# List recent builds
curl -sH "Authorization: Bearer $BUILDKITE_TOKEN" \
"https://api.buildkite.com/v2/organizations/mockserver/pipelines/mockserver-java/builds?per_page=10" | jq '.[].{state,branch,message,created_at}'
# Get a specific build
curl -sH "Authorization: Bearer $BUILDKITE_TOKEN" \
"https://api.buildkite.com/v2/organizations/mockserver/pipelines/mockserver-java/builds/{build_number}"
# Get build log output for a job
curl -sH "Authorization: Bearer $BUILDKITE_TOKEN" \
"https://api.buildkite.com/v2/organizations/mockserver/pipelines/mockserver-java/builds/{build_number}/jobs/{job_id}/log"
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 · 121 lines · 44 tokens per session scan A 4e222c75f1e3
pipeline-investigator is an agent published in the GitHub repository mock-server/mockserver-monorepo (4,969 stars, last pushed today), licensed Apache-2.0. It adds 44 tokens to every session and 1,198 once invoked, about $0.0002 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 agents, from other repositories
retrospective
Reflective analyst who extracts learnings through structured retrospective frameworks, diagnosing agent performance, identifying error patterns, and documenting success strategies. Uses Five Whys, timeline analysis, and learning matrices. Use when you need root-cause analysis, atomicity scoring, or to transform…
ci-debugger
CI pipeline debugging specialist. Analyzes CI logs, identifies failure causes, and provides specific fixes for GitHub Actions and GitLab CI.
ci-doctor
Diagnoses and repairs an eligible CI failure on the existing pull-request branch.
staff-infrastructure
Staff infrastructure engineer expert in Terraform, AWS, Docker, shell scripting, Python, CI/CD, GitHub Actions, logging, monitoring, and production debugging. Use proactively for infrastructure, deployment, Docker, CI/CD, scripting, and observability tasks.
debug
Debug your application to find and fix a bug. Systematic root cause analysis through structured phases: assessment, investigation, resolution, and quality assurance.
orc-ci-investigator
Investigator role — diagnoses a failing CI run end-to-end and returns a classified failure report with a concrete fix list; never edits code, never re-runs workflows. Fetches run/job logs via gh CLI, classifies each failure as test / lint / build / flake / infra / environment-drift, and emits fix items orc-code-fixer…