physical-capability-cloud: Command for Claude Code

.claude/commands/pcc-discover.md

pcc-discover is a command for Claude Code from global-mysterysnailrevolution/physical-capability-cloud. It costs 0 tokens per session (1,526 once invoked), scanned A, original, Apache-2.0.

Command-line tools for finding devices on a local network and onboarding them to the PCC network. PCC is a system that registers equipment and its capabilities for use by operators.

In plain words
What is it for?
Scanning for printers, CNC machines, and lab instruments, checking setup status, generating kernel configuration, and automatically registering discoverable devices.
Why use it?
They reduce the manual work of discovering equipment, checking setup, generating configuration, and registering devices.

Command for Claude Code

Written for Claude Code: installed under .claude/.

This is global-mysterysnailrevolution/physical-capability-cloud's own configuration. It tells Claude Code how to work on physical-capability-cloud itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything physical-capability-cloud configures →

Needs its repository: it runs a file that does not travel with it, so clone the repository first. The line is node packages/mcp-server/dist/cli.js discover scan.

Reuse

Borrowing it

Nothing to install: this file belongs to global-mysterysnailrevolution/physical-capability-cloud. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/global-mysterysnailrevolution/physical-capability-cloud/master/.claude/commands/pcc-discover.md
Clone the repo
git clone --depth 1 https://github.com/global-mysterysnailrevolution/physical-capability-cloud

Made for: Claude Code.

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 pcc-discover

README.md
[![agentmods](https://agentmods.dev/badge/commands/global-mysterysnailrevolution/physical-capability-cloud/pcc-discover/github.svg)](https://agentmods.dev/commands/global-mysterysnailrevolution/physical-capability-cloud/pcc-discover)
Your own site
<a href="https://agentmods.dev/commands/global-mysterysnailrevolution/physical-capability-cloud/pcc-discover"><img src="https://agentmods.dev/badge/commands/global-mysterysnailrevolution/physical-capability-cloud/pcc-discover/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.

agentmods 80×15 button for pcc-discover

Your own site · 80×15
<a href="https://agentmods.dev/commands/global-mysterysnailrevolution/physical-capability-cloud/pcc-discover"><img src="https://agentmods.dev/badge/commands/global-mysterysnailrevolution/physical-capability-cloud/pcc-discover.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,526 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.00000 $0.01526
Opus 5 $0.00000 $0.00763
Sonnet 5 $0.00000 $0.00305
Haiku 4.5 $0.00000 $0.00153

Measured 11d ago against content hash 16a15b823974, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

pcc-discover 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.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

.claude/commands/pcc-discover.md · 164 lines

How it starts

The opening of the file, as written. The whole thing — 164 lines — stays where its author put it; the contents beside it link to each section on GitHub.

PCC Discover — CLI

Device discovery, network scanning, and full operator onboarding — from zero to a registered, verified kernel.

When to use

  • "Help me onboard a new device"
  • "Set up a kernel"
  • "Scan the network for devices"
  • "Register my 3D printer / CNC / HPLC on PCC"
  • "Configure a new shop kernel"
  • "Check if my device is set up correctly"
  • "Run the setup wizard"
  • "What's my setup status?"

Prerequisites

  • Build the CLI first: cd packages/mcp-server && npx tsc
  • Gateway reachable at PCC_URL (default: https://pcc-gateway-production.up.railway.app)
  • For device registration: the physical device must be network-accessible from the machine running the CLI

Commands

Discover Scan — Find Devices on the Network

node packages/mcp-server/dist/cli.js discover scan

Scans the local network using mDNS and IPP discovery to find devices (printers, CNC machines, lab instruments) that can be registered on PCC. Returns a list of discovered devices with their type, IP address, and auto-detected capability type. Run this first when adding new equipment.

Discover Onboard — One-Command Auto-Onboarding

node packages/mcp-server/dist/cli.js discover onboard

Full pipeline in one command: scan → identify device → generate CSD → register on PCC. Best for standard equipment (OctoPrint printers, IPP-compatible devices). For custom or complex equipment, use the step-by-step setup commands below.

Setup Detect — Check Configuration State

node packages/mcp-server/dist/cli.js setup detect

Auto-detects the current configuration state. Reports what's already set up (kernel config, registered devices, env file) and what's missing. Always run this first before starting a manual setup — it tells you exactly where to begin.

Setup Config — Generate Kernel Configuration

node packages/mcp-server/dist/cli.js setup config

Interactively generates a KERNEL_CONFIG JSON from device descriptions. Asks about equipment type, adapter protocol (OctoPrint, Modbus RTU, OPC-UA, SiLA2), capabilities, and pricing. Outputs configuration you can save to kernel-config.json or set as KERNEL_CONFIG_FILE.

Read the full file on GitHub · 164 lines

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. 11d ago First seen · 164 lines · 0 tokens per session scan A 16a15b823974

Subscribe to this mod's changes

pcc-discover is a command published in the GitHub repository global-mysterysnailrevolution/physical-capability-cloud (5 stars, last pushed 5mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 1,526 tokens. 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.