A command-line tool for finding available laboratory or manufacturing capabilities and building priced work contracts. A capability is a type of service or equipment, such as CNC machining or mass spectrometry.

Listing and searching capability types, finding required parameters, pricing jobs, building contracts, and compiling multi-step workflows.

It helps turn a technical job into a defined workflow with required details, pricing, and a contract ready for escrow, which holds payment until agreed conditions are met.

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-build.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-build/github.svg)](https://agentmods.dev/commands/lamasu/physical-capability-cloud/pcc-build)

Your own site

<a href="https://agentmods.dev/commands/lamasu/physical-capability-cloud/pcc-build"><img src="https://agentmods.dev/badge/commands/lamasu/physical-capability-cloud/pcc-build/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-build"><img src="https://agentmods.dev/badge/commands/lamasu/physical-capability-cloud/pcc-build.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,634 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.01634
Opus 5.5	$0.00000	$0.00654
Sonnet 5.5	$0.00000	$0.00327
Haiku 4.5	$0.00000	$0.00163

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

Security

Grade A, and why

pcc-build 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-build — 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-build.md · 153 lines

How it starts

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

PCC Build — CLI

Capability discovery, contract construction, and pricing — from "what can PCC do?" to a signed contract ready for escrow.

When to use

"Build a contract for CNC machining"
"Price a 3D print job"
"What capabilities are available?"
"How much does HPLC analysis cost?"
"Search for flow chemistry capabilities"
"Build a contract for Tier 2 assurance"
"Compile a multi-step workflow"
"What parameters do I need for mass spectrometry?"

Prerequisites

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

Commands

Capabilities List — List All Capability Types

node packages/mcp-server/dist/cli.js capabilities list

Lists all registered capability types in the PCC taxonomy. Returns type identifiers (e.g., hplc, cnc-3axis, cnc-5axis, fdm-printer, mass-spec, flow-reactor, sla-printer, injection-molding). Use these type IDs in subsequent build commands.

Capabilities Search — Search Templates with Details

node packages/mcp-server/dist/cli.js capabilities search

Searches capability templates with full details: operator name, location, assurance tier, pricing, key specifications, and availability. Supports free-text search — describe what you need and it returns matching templates. Equivalent to browsing the PCC marketplace.

Build Options — Get Parameters for a Capability Type

node packages/mcp-server/dist/cli.js build options <type>

Returns the full parameter schema for a given capability type. Shows all configurable parameters, valid values, and interdependencies. Parameters are grouped (e.g., material, tolerance, quantity, assurance tier). Use the output to understand what values you'll need to provide.

Example:

node packages/mcp-server/dist/cli.js build options cnc-3axis

You can also pass partial selections to get context-dependent options:

node packages/mcp-server/dist/cli.js build options cnc-3axis --params '{"material":"aluminum"}'

This returns the options that depend on the already-selected material (e.g., achievable tolerances for aluminum).

Read the full file on GitHub · 153 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 · 153 lines · 0 tokens per session scan A 7f6eee69c5c9

Subscribe to this mod's changes

pcc-build 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 1,634 tokens. A static security scan graded it A with 0 findings. It is 100% identical to pcc-build, differing in 0 lines, and is treated as a copy.

E-commerce Planning

pcc-build next to 6 commands from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
pcc-buildLamaSu/physical-capability-cloud	Command	3	5d ago	Apache-2.0	A	0	Claude Code
devvendurehq/vendure	Command	8.6k	yesterday	none	A	0	Claude Code
startvendurehq/vendure	Command	8.6k	yesterday	none	A	0	Claude Code
sync-medusa-docs-changesmedusajs/medusa-agent-skills	Command	235	2d ago	none	A	0	GitHub Copilot
validate-ideakhadinakbarlabs/shopify-app-builder	Command	2	27d ago	MIT	A	13	Claude Code
ebay-ordersjbwashington/ebay-mcp	Command	17	8mo ago	MIT	A	8	Claude Code
docker-logslroy-stack/ai-pod-store	Command	1	11d ago	none	A	0	Claude Code

physical-capability-cloud: Command for Claude Code