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-ipgit 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.01424 |
| Opus 5 | $0.00000 | $0.00712 |
| Sonnet 5 | $0.00000 | $0.00285 |
| Haiku 4.5 | $0.00000 | $0.00142 |
Grade A, and why
pcc-ip 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-ip — 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 — 139 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PCC IP — CLI
Register capabilities as Story Protocol IP Assets, track royalties, claim revenue, and configure revenue splits.
When to use
- "Register this CSD as IP"
- "Check my royalties"
- "Claim my IP revenue"
- "Show the IP lineage for this capability"
- "Set up revenue splits"
- "How much have I earned from my HPLC protocol IP?"
- "Who are the upstream IPs I owe royalties to?"
- "Configure splits between the lab and the developer"
Prerequisites
- Build the CLI first:
cd packages/mcp-server && npx tsc - Gateway reachable at
PCC_URL(default: https://pcc-gateway-production.up.railway.app) - CSD must already be registered (
/pcc-csd) before registering it as IP
Commands
IP Register — Register Capability as IP Asset
node packages/mcp-server/dist/cli.js ip register
Registers a CSD (Capability StructureDefinition) as a Story Protocol IP Asset. Creates an on-chain IP record with provenance anchored to the CSD's canonical URI. Returns the Story Protocol IP Asset ID (ipId) which you use in all subsequent IP commands.
Provide the CSD URI and optional metadata:
node packages/mcp-server/dist/cli.js ip register --csd-uri "https://pcc.example.com/csd/hplc-reverse-phase-v1" --name "HPLC Reverse Phase Protocol" --description "Validated pharma-grade purity analysis protocol"
IP Revenue — Revenue Snapshot
node packages/mcp-server/dist/cli.js ip revenue <ipId>
Returns a snapshot of the IP Royalty Vault for the given IP Asset: total accumulated revenue, unclaimed balance, claimed-to-date, and revenue sources (which downstream IP Assets have paid royalties into this vault).
Example:
node packages/mcp-server/dist/cli.js ip revenue ip-asset-abc123
IP Claim — Claim Revenue
node packages/mcp-server/dist/cli.js ip claim <ipId>
Claims all accumulated unclaimed revenue from the IP Royalty Vault to the vault's designated recipient address. Triggers an on-chain transaction. Returns the claim transaction hash and amount claimed.
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 · 139 lines · 0 tokens per session scan A 0d3637271138
pcc-ip 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,424 tokens. A static security scan graded it A with 0 findings. It is 100% identical to pcc-ip, 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.