A command-line tool for managing Capability StructureDefinitions, which are versioned schema documents describing what a capability accepts, requires, and considers successful. FHIR is a healthcare data standard; this tool uses a similar structured approach for capability definitions.

Listing, viewing, and registering definitions for operations such as HPLC analysis, flow chemistry, CNC machining, and custom milling.

It provides one authoritative place to inspect capability inputs, evidence requirements, success criteria, lifecycle status, and type.

How global-mysterysnailrevolution/physical-capability-cloud configures

Reuse

Borrowing it

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

Clone the repo

git clone --depth 1 https://github.com/global-mysterysnailrevolution/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/global-mysterysnailrevolution/physical-capability-cloud/pcc-csd/github.svg)](https://agentmods.dev/commands/global-mysterysnailrevolution/physical-capability-cloud/pcc-csd)

Your own site

<a href="https://agentmods.dev/commands/global-mysterysnailrevolution/physical-capability-cloud/pcc-csd"><img src="https://agentmods.dev/badge/commands/global-mysterysnailrevolution/physical-capability-cloud/pcc-csd/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/global-mysterysnailrevolution/physical-capability-cloud/pcc-csd"><img src="https://agentmods.dev/badge/commands/global-mysterysnailrevolution/physical-capability-cloud/pcc-csd.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,622 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 original No closer match found 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.01622
Opus 5	$0.00000	$0.00811
Sonnet 5	$0.00000	$0.00324
Haiku 4.5	$0.00000	$0.00162

Measured 10d ago against content hash 10b4a1d09727, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

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 10d 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

Copies of this mod

1 near-identical copy found in the catalogue:

pcc-csd — 100% identical, 0 lines differ

.claude/commands/pcc-csd.md · 154 lines

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.

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

10d ago First seen · 154 lines · 0 tokens per session scan A 10b4a1d09727

Subscribe to this mod's changes

pcc-csd is a command published in the GitHub repository global-mysterysnailrevolution/physical-capability-cloud (5 stars, last pushed 5mo 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. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Building agents

physical-capability-cloud: Command for Claude Code

Borrowing it

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Nothing flagged

Copies of this mod

How it starts

PCC CSD — CLI

When to use

Prerequisites

What is a CSD?

Commands

CSD List — List All CSDs

CSD Get — Get a Specific CSD

What this file has done since we first saw it

Other commands, from other repositories

checklist

clarify

specify

analyze

converge

implement