A command-line tool for adding a new machine, device, or capability to the PCC network. It can inspect configuration, find network devices such as printers, and register them in the PCC registry.

Use it to onboard machines, printers, kernels, or CNC mills; scan for IPP devices; generate device configuration; and run the onboarding pipeline.

It reduces the manual work of discovering equipment, preparing its configuration, and registering it with the network.

How LamaSu/physical-capability-cloud configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to LamaSu/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/LamaSu/physical-capability-cloud/master/.claude/commands/pcc-onboard.md

Clone the repo

git clone --depth 1 https://github.com/LamaSu/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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/lamasu/physical-capability-cloud/pcc-onboard/github.svg)](https://agentmods.dev/commands/lamasu/physical-capability-cloud/pcc-onboard)

Your own site

<a href="https://agentmods.dev/commands/lamasu/physical-capability-cloud/pcc-onboard"><img src="https://agentmods.dev/badge/commands/lamasu/physical-capability-cloud/pcc-onboard/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.

Your own site · 80×15

<a href="https://agentmods.dev/commands/lamasu/physical-capability-cloud/pcc-onboard"><img src="https://agentmods.dev/badge/commands/lamasu/physical-capability-cloud/pcc-onboard.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 925 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 100% copy Near-identical to another mod 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.

Model	Per session	Once invoked
Fable 5.1	$0.00000	$0.00925
Opus 5.5	$0.00000	$0.00370
Sonnet 5.5	$0.00000	$0.00185
Haiku 4.5	$0.00000	$0.00093

Measured 2mo ago against content hash 03e4e29606cc, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

pcc-onboard 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 2mo 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

This is a copy

100% identical to pcc-onboard — 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.

.claude/commands/pcc-onboard.md · 92 lines

How it starts

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

PCC Onboard — CLI

Onboard a new machine or capability to the PCC network using CLI tools.

When to use

"I have a new machine to add" / "Onboard my printer" / "Register equipment"
"Set up a new kernel" / "Add my CNC mill to PCC"

Prerequisites

PCC gateway reachable at PCC_URL (default: https://pcc-gateway-production.up.railway.app)
Build CLI: cd packages/mcp-server && npx tsc

Commands

Auto-detect configuration state

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

Check what's configured, what env vars are set, database status. Start here.

Scan for devices on network

node packages/mcp-server/dist/cli.js discover scan [--protocols=ipp] [--timeout=3000] [--pretty]

Find IPP printers and other discoverable devices on the local network.

One-command onboard pipeline

node packages/mcp-server/dist/cli.js discover onboard [--uri=ipp://192.168.1.50/ipp/print] [--protocol=ipp] [--pretty]

Auto-discover → generate CSD → register in PCC registry. All in one command.

Generate kernel config

node packages/mcp-server/dist/cli.js setup config '<devicesJson>' [--kernelId=my-shop] [--mockMode] [--pretty]

Generate KERNEL_CONFIG JSON from device descriptions. The devicesJson is an array of {name, type, adapterType, url?, apiKey?, host?, port?}.

Validate config

node packages/mcp-server/dist/cli.js setup validate [--config='{}'] [--pretty]

Check adapter connectivity and config completeness. Omit --config to validate current.

Register a device

node packages/mcp-server/dist/cli.js setup register-device --kernelId=x --deviceId=y --type=machine|sensor|camera --adapter=octoprint|modbus|opcua|sila|generic-http|mock [--model="Prusa MK4"] [--pretty]

Health check

node packages/mcp-server/dist/cli.js setup health [--deviceId=x] [--pretty]

Connectivity status and response time for all or specific devices.

Run test job

node packages/mcp-server/dist/cli.js setup test-job [--kernelId=x] [--deviceId=y] [--tier=0] [--pretty]

End-to-end pipeline test: submit → execute → evidence → (optional) settlement.

Read the full file on GitHub · 92 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.

2mo ago First seen · 92 lines · 0 tokens per session scan A 03e4e29606cc

Subscribe to this mod's changes

pcc-onboard is a command published in the GitHub repository LamaSu/physical-capability-cloud (3 stars, last pushed 5d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 925 tokens. A static security scan graded it A with 0 findings. It is 100% identical to pcc-onboard, differing in 0 lines, and is treated as a copy.

DevOps and cloud Hardware and IoT

pcc-onboard next to 6 commands from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
pcc-onboardLamaSu/physical-capability-cloud	Command	3	5d ago	Apache-2.0	A	0	Claude Code
tapeoutrjwalters/kicad-tools	Command	73	yesterday	MIT	A	0	Claude Code
eol-reportWYRE-AI/msp-claude-plugins	Command	52	yesterday	Apache-2.0	A	28	Claude Code
rvcsi-calibrateruvnet/rvcsi	Command	28	25d ago	Apache-2.0	A	20	Claude Code
esp-hardenmathisk2095/jko-claude-plugins	Command	3	24d ago	MIT	A	17	Claude Code
pentest-wirelessJoasASantos/ClaudeAdvancedPlugins	Command	160	8mo ago	MIT	A	0	Claude Code
device-infophinn/KinetAios	Command	12	yesterday	GPL-3.0	A	22	Claude Code

physical-capability-cloud: Command for Claude Code