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.
curl -O https://raw.githubusercontent.com/global-mysterysnailrevolution/physical-capability-cloud/master/.claude/commands/pcc-identity.mdgit clone --depth 1 https://github.com/global-mysterysnailrevolution/physical-capability-cloudWrote 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.
[](https://agentmods.dev/commands/global-mysterysnailrevolution/physical-capability-cloud/pcc-identity)<a href="https://agentmods.dev/commands/global-mysterysnailrevolution/physical-capability-cloud/pcc-identity"><img src="https://agentmods.dev/badge/commands/global-mysterysnailrevolution/physical-capability-cloud/pcc-identity/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.
<a href="https://agentmods.dev/commands/global-mysterysnailrevolution/physical-capability-cloud/pcc-identity"><img src="https://agentmods.dev/badge/commands/global-mysterysnailrevolution/physical-capability-cloud/pcc-identity.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.01471 |
| Opus 5 | $0.00000 | $0.00736 |
| Sonnet 5 | $0.00000 | $0.00294 |
| Haiku 4.5 | $0.00000 | $0.00147 |
Grade A, and why
pcc-identity 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 11d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- pcc-identity — 92% identical, 2 lines differ
How it starts
The opening of the file, as written. The whole thing — 138 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PCC Identity — CLI
Agent identity, ERC-8004 registration files, and reputation scores for machines and agents on the PCC network.
When to use
- "Get agent identity"
- "Check registration status"
- "Show the ERC-8004 identity for kernel-01"
- "Get the agent registration file"
- "What's the reputation of this agent?"
- "Show me who I am on PCC"
- "Is my agent registered?"
- "Show reputation by tag"
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 ERC-8004?
ERC-8004 is PCC's on-chain identity standard for machines and autonomous agents. It defines three registries:
| Registry | What It Stores |
|---|---|
| Identity Registry | DID, capabilities list, service endpoints, owner address |
| Reputation Registry | Reputation scores, job history, dispute outcomes, verifier endorsements |
| Validation Registry | Certifications, assurance tier qualifications, third-party attestations |
Every Shop Kernel, User Agent, Broker Agent, and Evaluator Agent has an ERC-8004 identity. The agent-registration.json file (also called the Agent Registration File or ARF) is a standardized off-chain document that describes an agent's tools, capabilities, and A2A endpoints — analogous to a DNS record for agents.
Commands
Agents Identity — ERC-8004 Identity
node packages/mcp-server/dist/cli.js agents identity <agentId>
Returns the full ERC-8004 identity record for a given agent or kernel. Output includes:
- DID (did:pcc or did:key format)
- Owner address (on-chain wallet controlling this identity)
- Agent type (kernel / user / broker / evaluator / support)
- Registered capabilities (list of capability types this agent supports)
- Service endpoints (A2A intent endpoints, MCP endpoint, REST endpoint)
- Validation certifications (assurance tier qualifications from the Validation Registry)
- Registration timestamp and last-updated block
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.
- 11d ago First seen · 138 lines · 0 tokens per session scan A 413d4744edb1
pcc-identity 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,471 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.
Other commands, from other repositories
deploy
Deploy Solana program (devnet first, then mainnet).
invariant
Generate Foundry invariant tests for property-based fuzzing. The high-value command for serious teams.
audit-strict
Multi-pass consensus audit — runs the audit twice with different prompts, only reports consensus findings. Aggressively cuts false positives.
docs-remove
Remove a user-defined source alias from sources.yaml, optionally deleting its cached Markdown.
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.