investigate

investigate is a command for Claude Code from ProductionMasterAI/production-master. It costs 24 tokens per session (203 once invoked), scanned A, original, MIT.

A command that starts an investigation on the hosted Production Master service and shows live progress in the editor. The investigation itself runs on the service, not on your computer.

In plain words
What is it for?
Use it to send an investigation request, monitor its progress, read the report, and relay approval or rejection decisions.
Why use it?
It gives you a way to submit an investigation and follow its results without running the analysis locally.

Command for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

Runs only inside its plugin — its command needs a path that Claude Code sets for a plugin’s own hooks and for nothing else. Install the plugin, not this.

Part of the production-master plugin — 1 skill, 5 commands shipped together

Good fit Use it to send an investigation request, monitor its progress, read the…

Compare 6 commands from other repositories ↓
Install

Getting it into your agent

This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.

Claude Code
/plugin marketplace add ProductionMasterAI/production-master
Claude Code
/plugin install production-master

Made for: Claude Code.

Or install production-master, the plugin that ships this one along with the rest of its 1 skill, 5 commands.

Wrote 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.

agentmods badge for investigate

README.md
[![agentmods](https://agentmods.dev/badge/commands/productionmasterai/production-master/investigate.svg)](https://agentmods.dev/commands/productionmasterai/production-master/investigate)
Your own site
<a href="https://agentmods.dev/commands/productionmasterai/production-master/investigate"><img src="https://agentmods.dev/badge/commands/productionmasterai/production-master/investigate.svg" alt="Measured on agentmods" height="20"></a>
Per session 24 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 203 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00024 $0.00203
Opus 5 $0.00012 $0.00102
Sonnet 5 $0.00005 $0.00041
Haiku 4.5 $0.00002 $0.00020

Measured 6d ago against content hash 7ffca27fac12, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

investigate 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 6d 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.

commands/investigate.md · 22 lines

What it actually says

Trigger an investigation for: $ARGUMENTS

The run executes entirely on the Production Master hosted service. This command only authenticates, triggers the run, streams live progress, renders the report, and relays any approve/reject decisions — no analysis happens locally. If you are not logged in, run /login first.

set -euo pipefail
PLUGIN_ROOT="${CLAUDE_PLUGIN_ROOT:-$(pwd)}"
CLI="${PLUGIN_ROOT}/packages/adapter-claude-code/dist/cli.js"
[ -f "$CLI" ] || CLI="${PLUGIN_ROOT}/dist/cli.js"
export PM_SERVICE_URL="${PM_SERVICE_URL:-https://api.productionmaster.dev}"
node "$CLI" investigate --input "$ARGUMENTS"
Changes

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.

  1. 6d ago First seen · 22 lines · 24 tokens per session scan A 7ffca27fac12

Subscribe to this mod's changes

investigate is a command published in the GitHub repository ProductionMasterAI/production-master (0 stars, last pushed 2d ago), licensed MIT. It adds 24 tokens to every session and 203 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-31.