Borrowing it
Nothing to install: this file belongs to ProductionMasterAI/production-master-mcp. 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/ProductionMasterAI/production-master-mcp/main/.claude/skills/run-production-master-mcp/SKILL.mdgit clone --depth 1 https://github.com/ProductionMasterAI/production-master-mcpWrote 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/productionmasterai/production-master-mcp/run-production-master-mcp)<a href="https://agentmods.dev/skills/productionmasterai/production-master-mcp/run-production-master-mcp"><img src="https://agentmods.dev/badge/skills/productionmasterai/production-master-mcp/run-production-master-mcp/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/productionmasterai/production-master-mcp/run-production-master-mcp"><img src="https://agentmods.dev/badge/skills/productionmasterai/production-master-mcp/run-production-master-mcp.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.00067 | $0.00587 |
| Opus 5 | $0.00034 | $0.00293 |
| Sonnet 5 | $0.00013 | $0.00117 |
| Haiku 4.5 | $0.00007 | $0.00059 |
Grade A, and why
run-production-master-mcp 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 11d 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
run-production-master-mcp
Local verification and run helper for this npm-workspaces monorepo. Run every gate the way
CI does, in order, and stop at the first failure. Prefer the make targets (they wrap the
npm scripts).
Verify
-
Install — clean, reproducible install from the lockfile:
make install # npm ci -
Build all workspaces — compile every package under
packages/*:make build # npm run build -
Test — run the full test suite:
make test # npm test -
Lint — the same lint gate CI enforces (warnings fail the build):
make lint # npm run lint -
Typecheck — a stricter pass than build (also part of CI):
npm run typecheck
Run the server locally
Set PM_API_URL to the Production Master REST API base and (for stdio) PM_SESSION_JWT
to your session token, then:
# stdio transport (default)
PM_API_URL=<api-base-url> PM_SESSION_JWT=<your-token> \
npm run dev --workspace=@production-master/mcp
# Streamable HTTP transport — POST /mcp on PM_MCP_HTTP_PORT (default 3000);
# bearer is per-request, so no PM_SESSION_JWT here
PM_API_URL=<api-base-url> \
npm run dev --workspace=@production-master/mcp -- --http
make dev (npm run dev --workspaces --if-present) runs the same script across every
workspace that defines one — today that is just @production-master/mcp. Connect an MCP
client to it as described in
docs/user/quick-start.md; the full config reference
is docs/user/reference/commands.md.
Reporting
- Report each step as pass/fail with the command that proved it.
- On failure, show the failing output (trimmed) and stop — do not continue to later steps.
- Only report the repo as healthy when the verify steps all pass; cite the final command's output as evidence.
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.
- 11d ago First seen · 73 lines · 67 tokens per session scan A 2bcd34a274be
run-production-master-mcp is a skill published in the GitHub repository ProductionMasterAI/production-master-mcp (0 stars, last pushed today), licensed MIT. It adds 67 tokens to every session and 587 once invoked, about $0.0003 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-31.
Other skills, from other repositories
run-production-master
Build all workspaces, run tests, lint, and validate the install manifests for the production-master thin-client monorepo. Use before opening a PR or when verifying a local checkout is healthy. Triggers on "build and test", "run the checks", "validate manifests", "verify the repo".
gentle-ai-bench
Trigger: bench, journey, journeys, driven mode, gentle-ai-bench, journey corpus, j-numbers, bench axis. Author and verify gentle-ai bench journeys; go test ./bench never proves driven execution.
go-testing
Trigger: Go tests, go test coverage, Bubbletea teatest, golden files. Apply focused Go testing patterns.
remove-ai-slops
Removes AI-generated code smells from branch changes or an explicit file list behind regression tests. Use when the user asks to clean up, deslop, or remove AI-slop patterns from recent changes.
testing-anti-patterns
Reviews test code to identify and fix common testing anti-patterns including flaky tests, over-mocking, brittle assertions, test interdependency, and hidden test logic. Flags bad patterns, explains the specific defect, and provides corrected implementations. Use when reviewing test code, debugging intermittent or…
eval-leakage-audit
Audits whether a verification (eval/metric/experiment/holdout) actually secures independent external ground truth, or whether the designer, the model, and the scorer are just confirming each other in a circle — via a 21-pattern taxonomy. Read-only. Use before trusting any 'how we'll know it worked' — A/B tests…