Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/ProductionMasterAI/production-masterWrote 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/plugins/productionmasterai/production-master/plugin)<a href="https://agentmods.dev/plugins/productionmasterai/production-master/plugin"><img src="https://agentmods.dev/badge/plugins/productionmasterai/production-master/plugin/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/plugins/productionmasterai/production-master/plugin"><img src="https://agentmods.dev/badge/plugins/productionmasterai/production-master/plugin.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
production-master 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 4d 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
{
"name": "production-master",
"version": "0.2.0",
"description": "Thin client for the Production Master hosted incident-investigation service — start a run, follow its progress, read the report, and act on proposed changes from inside Claude Code. Connects to the hosted service's MCP endpoint; nothing runs on your machine.",
"icon": "./assets/icon.png",
"author": {
"name": "ProductionMasterAI",
"url": "https://github.com/ProductionMasterAI"
},
"homepage": "https://github.com/ProductionMasterAI/production-master#readme",
"repository": "https://github.com/ProductionMasterAI/production-master",
"license": "MIT",
"privacyPolicyUrl": "https://productionmaster.dev/privacy",
"keywords": [
"observability",
"debugging",
"incident-response",
"thin-client",
"mcp"
],
"userConfig": {
"api_token": {
"type": "string",
"title": "Production Master access token",
"description": "A personal access token from the Production Master console (Settings, then Access tokens). It is stored in your OS credential store and sent only to the Production Master service.",
"sensitive": true,
"required": true
}
},
"mcpServers": {
"production-master": {
"type": "http",
"url": "https://api.productionmaster.dev/v1/mcp",
"headers": {
"Authorization": "Bearer ${user_config.api_token}"
}
}
}
}
What it installs
The manifest is a name and a version. 4 commands travel with it, and installing the plugin installs all of them — 83 tokens a session between them. Each is measured on its own page, and each can be installed alone.
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.
- 4d ago Changed · +19 lines 0b86095b9f87
- 9d ago First seen · 21 lines scan A 906434c38985
production-master is a plugin published in the GitHub repository ProductionMasterAI/production-master (2 stars, last pushed 3d ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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-11-05.
production-master compared with plugins from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| production-masterProductionMasterAI/production-master | Plugin | 2 | 3d ago | MIT | A | — | Claude Code |
| distributed-debuggingwshobson/agents | Plugin | 43k | 6d ago | MIT | A | — | Claude Code |
| paparatsIBazylchuk/paparats-mcp | Plugin | 34 | 2d ago | MIT | A | — | Cursor |
| grepai-searchyoanbernabeu/grepai-skills | Plugin | 20 | 15d ago | MIT | A | — | Claude Code |
| visual-sentinelVisualSentinel/mcp-server | Plugin | 1 | 5d ago | MIT | A | — | Gemini CLI |
| vibelenssoumyachk101/VibeLens | Plugin | 0 | 1mo ago | MIT | A | — | Claude Code |
| forensic-deepdiveDhevenddra/forensic-deepdive | Plugin | 2 | 3mo ago | Apache-2.0 | A | — | Claude Code |