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-buildgit 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.01634 |
| Opus 5 | $0.00000 | $0.00817 |
| Sonnet 5 | $0.00000 | $0.00327 |
| Haiku 4.5 | $0.00000 | $0.00163 |
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 yesterday.
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-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.
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).
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.
- yesterday First seen · 153 lines · 0 tokens per session scan A 7f6eee69c5c9
pcc-build 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,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.
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.
constitution
Create or update the project constitution from interactive or provided principle inputs.