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.
npx agentmods add commands/lamasu/physical-capability-cloud/pcc-discovergit clone --depth 1 https://github.com/LamaSu/physical-capability-cloudWhat 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 | $0.00000 | $0.01526 |
| Opus 5 | $0.00000 | $0.00763 |
| Sonnet 5 | $0.00000 | $0.00305 |
| Haiku 4.5 | $0.00000 | $0.00153 |
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 2d 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.
This is a copy
100% identical to pcc-discover — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
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.
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.
- 2d ago First seen · 164 lines · 0 tokens per session scan A 16a15b823974
pcc-discover is a command published in the GitHub repository LamaSu/physical-capability-cloud (1 stars, last pushed 4d 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. It is 100% identical to pcc-discover, differing in 0 lines, and is treated as a copy.
Other commands, from other repositories
observe
部屋を能動的に観察する。3つの基本ブロックを自由に選びながらループし、受動的なスナップショットではなく発見のある観察を行う。.
model
Check if an AI model fits on your GPU before downloading.
tapeout
Produce a complete, fab-ready export bundle for a routed board — or refuse loudly. Superset of /kct:manufacturing-readiness: runs the three sign-off pre-gates, then adds a BOM part-number-resolution gate, a per-rule warning-review gate (assembly-affecting warnings block unless explicitly acknowledged), schematic +…
eol-report
EOL/EOS risk report — devices, OS versions, and firmware approaching or past end-of-life/end-of-support, prioritized by criticality.
rvcsi-calibrate
Learn a v0 per-subcarrier baseline (mean amplitude) from a .rvcsi capture.
iot
This API allows you to manage your IoT hubs and devices.