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-onboardgit clone --depth 1 https://github.com/LamaSu/physical-capability-cloudWrote 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/commands/lamasu/physical-capability-cloud/pcc-onboard)<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="Measured on agentmods" height="20"></a>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 | $0.00000 | $0.00925 |
| Opus 5 | $0.00000 | $0.00463 |
| Sonnet 5 | $0.00000 | $0.00185 |
| Haiku 4.5 | $0.00000 | $0.00093 |
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 3d 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-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.
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.
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.
- 3d ago First seen · 92 lines · 0 tokens per session scan A 03e4e29606cc
pcc-onboard is a command published in the GitHub repository LamaSu/physical-capability-cloud (1 stars, last pushed yesterday), 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.
Other commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.