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-csdgit 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.01622 |
| Opus 5 | $0.00000 | $0.00811 |
| Sonnet 5 | $0.00000 | $0.00324 |
| Haiku 4.5 | $0.00000 | $0.00162 |
Grade A, and why
pcc-csd 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-csd — 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 — 154 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PCC CSD — CLI
Manage Capability StructureDefinitions — the FHIR-inspired schema layer that defines what capabilities can do, their parameters, and their lifecycle.
When to use
- "List capability definitions"
- "Register a new CSD"
- "Get the CSD for HPLC reverse phase"
- "What CSDs are available for flow chemistry?"
- "Create a CSD for my custom milling operation"
- "Show me the active base CSDs"
- "What parameters does the CNC-5axis CSD define?"
Prerequisites
- Build the CLI first:
cd packages/mcp-server && npx tsc - Gateway reachable at
PCC_URL(default: https://pcc-gateway-production.up.railway.app)
What is a CSD?
A Capability StructureDefinition (CSD) is a versioned schema document that formally defines a PCC capability. It specifies:
- Parameters: What inputs the capability accepts (materials, tolerances, methods)
- Evidence requirements: What data must be collected per assurance tier
- Acceptance criteria: What constitutes a successful outcome
- Lifecycle status:
draft,active,retired - Kind:
base(canonical type),profile(specialization),extension(adds fields),workflow(multi-step)
CSDs are the authoritative source of truth for what a capability contract can contain. The contract builder (/pcc-build) is backed by CSDs.
Commands
CSD List — List All CSDs
node packages/mcp-server/dist/cli.js csd list
Lists all registered CSD documents. Returns: canonical URI, name, kind, status, version, and registration date.
Filter by kind:
node packages/mcp-server/dist/cli.js csd list --kind base
node packages/mcp-server/dist/cli.js csd list --kind profile
node packages/mcp-server/dist/cli.js csd list --kind workflow
Filter by status:
node packages/mcp-server/dist/cli.js csd list --status active
node packages/mcp-server/dist/cli.js csd list --status draft
CSD Get — Get a Specific CSD
node packages/mcp-server/dist/cli.js csd get <uri>
Retrieves the full CSD document by its canonical URI. Output is the complete JSON schema including all parameter definitions, evidence requirements, and acceptance criteria.
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 · 154 lines · 0 tokens per session scan A 10b4a1d09727
pcc-csd 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,622 tokens. A static security scan graded it A with 0 findings. It is 100% identical to pcc-csd, differing in 0 lines, and is treated as a copy.
Other commands, from other repositories
OPSX: Fast Forward
Create a change and generate all artifacts needed for implementation in one go.
medical-necessity
Generate medical necessity letters citing chiropractic clinical guidelines for insurance authorization and appeals.
wh:asta-lit
Use when the user wants to find literature with Asta Paper Finder and ingest the results into the Wheeler knowledge graph.
gpd:derive-equation
Perform a rigorous physics derivation with systematic verification at each step.
run-panguweather
Guide the user through running PanguWeather end-to-end on an AMD cluster.
unity-test
Writes missing tests and runs them via MCP. Identifies untested code, creates EditMode/PlayMode tests, executes via runtests, reports results.