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/github-pipeline-audit/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/github-pipeline-audit)<a href="https://agentmods.dev/skills/mock-server/mockserver-monorepo/github-pipeline-audit"><img src="https://agentmods.dev/badge/skills/mock-server/mockserver-monorepo/github-pipeline-audit/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/github-pipeline-audit"><img src="https://agentmods.dev/badge/skills/mock-server/mockserver-monorepo/github-pipeline-audit.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to high
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 →
- high Supply Chain · line 296 Remote code is downloaded and executed. This bypasses code review and could introduce malicious code.Fix: Avoid downloading and executing remote scripts. Use trusted packages from PyPI/npm. If remote fetch is required, verify checksums and use HTTPS.
- low Supply Chain · line 295 Remote code is downloaded and executed. This bypasses code review and could introduce malicious code.Fix: Avoid downloading and executing remote scripts. Use trusted packages from PyPI/npm. If remote fetch is required, verify checksums and use HTTPS.
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.00119 | $0.04191 |
| Opus 5.5 | $0.00048 | $0.01676 |
| Sonnet 5.5 | $0.00024 | $0.00838 |
| Haiku 4.5 | $0.00012 | $0.00419 |
Grade B, and why
github-pipeline-audit scanned grade B with 2 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 today.
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.
Downloads and executes remote codemediumSupply chain
curl | sh runs whatever the server returns today, which is not necessarily what it returned when this was reviewed.
| PyPI | `curl -s https://pypi.org/pypi/mockserver-client/json \| python3 -c "import sys,json;print(json.load(sys.stdin)['info']['version'])"` | Downgraded: this mod is about security review, or the phrase is quoted, so it is likely naming the pattern rather than instructing it.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
| Maven Central | `curl -s https://repo1.maven.org/maven2/org/mock-server/mockserver-netty/maven-metadata.xml \| grep -E '<latest>\|<release>'` | How it starts
The opening of the file, as written. The whole thing — 358 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub + Build Pipeline Audit
Confirm that nothing is outstanding across GitHub and CI, and that everything that should be current is current.
Outcome
Produce a clean-state report: one row per surface, each either CLEAN or with a
precise, actionable finding. The audit is only complete when every surface in the
checklist below has been positively checked — "I didn't see anything" is not a result,
CLEAN requires having run the query.
The governing principle: a green PR check is not the same as a healthy pipeline. Several of the most damaging conditions this repo has hit are invisible from the PR and issue lists — the Dependabot updater silently failing so no security PRs are ever raised, a stale dependency-graph snapshot generating dozens of phantom alerts, a local checkout hundreds of commits behind. Sections 2, 5 and 6 exist specifically to catch the failures that do not announce themselves.
Prerequisites
gh auth status --hostname github.com # needs repo scope
bk api "user" >/dev/null && echo "bk CLI ok"
ghCLI authenticated (orGITHUB_TOKENwithreposcope).- The locally-authenticated
bkCLI for Buildkite. Do not use the Buildkite API tokens in AWS Secrets Manager for logs — they deliberately lack theread_build_logsscope and return"doesn't have the read_build_logs scope". They are fine for build state, triggering and retrying. - The
ghtoken typically lacksread:project, soprojectsV2GraphQL queries fail. That is expected — report Projects as "not checkable with current token scopes" rather than as clean.
Set once:
R=mock-server/mockserver-monorepo
0. Check the checkout is current — do this FIRST
Every subsequent version claim depends on it. A stale checkout produces confident, wrong answers: it will report already-fixed vulnerabilities as open, and validating a merged fix against it yields a false negative.
git fetch origin
git rev-list --count master..origin/master # MUST be 0
git status -sb | head -3
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.
- today Changed 9452eb80c90f
- 5d ago Changed dc838914a4be
- 11d ago Changed 72357082db9f
- 1mo ago Changed 2c1dc153398b
- 1mo ago First seen · 358 lines · 119 tokens per session scan B a2efb104892b
github-pipeline-audit is a skill published in the GitHub repository mock-server/mockserver-monorepo (4,999 stars, last pushed today), licensed Apache-2.0. It adds 119 tokens to every session and 4,191 once invoked, about $0.0005 per session on Opus 5.5. A static security scan graded it B with 2 findings (downloads and executes remote code, 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
bmad-loop
Iterate over a list of story keys, executing dev → review → PR → CI → merge for each. Use when the user says "loop these stories [list]" or "run the loop on [story keys]".
merge-batch
Prepare and merge an owner-selected PR batch with contributor credit and exact-candidate admission. Use for a pasted PR list; combined focused validation is diagnostic, and every actual landing still requires its applicable checks and authorization.
prowler-commit
Creates professional git commits following conventional-commits format. Trigger: When creating commits, after completing code changes, when user asks to commit.
gh-auth-isolation
Safely manage multiple GitHub identities (EMU + personal) in agent workflows.
comet-github
A routing guide for Comet-related GitHub work. It directs requests about pull requests, issues, CI failures, ideas, and fixes to the appropriate review or implementation process.
release-helper
Ensures configuration and code changes are released correctly. Use PROACTIVELY whenever you edit config.json, change any setting, or fix a configuration bug in this project, so the change reaches production.