What is pcc-evidence?

A command-line tool for browsing evidence bundles, the records and verification results attached to jobs and their milestones.

Use it to list or inspect evidence for a job, check whether a proof is ready, see available verification protocols, or verify evidence for a milestone.

It gathers evidence status in one view, including encrypted references, IPFS storage identifiers, zero-knowledge proof status, verification scores, and evaluator attestations.

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-evidence.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-evidence/github.svg)](https://agentmods.dev/commands/global-mysterysnailrevolution/physical-capability-cloud/pcc-evidence)

Your own site

<a href="https://agentmods.dev/commands/global-mysterysnailrevolution/physical-capability-cloud/pcc-evidence"><img src="https://agentmods.dev/badge/commands/global-mysterysnailrevolution/physical-capability-cloud/pcc-evidence/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-evidence"><img src="https://agentmods.dev/badge/commands/global-mysterysnailrevolution/physical-capability-cloud/pcc-evidence.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,274 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.01274
Opus 5.5	$0.00000	$0.00510
Sonnet 5.5	$0.00000	$0.00255
Haiku 4.5	$0.00000	$0.00127

Measured 2mo ago against content hash 7f23eadf24c1, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

pcc-evidence 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 2mo 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-evidence — 100% identical, 0 lines differ

.claude/commands/pcc-evidence.md · 123 lines

How it starts

The opening of the file, as written. The whole thing — 123 lines — stays where its author put it; the contents beside it link to each section on GitHub.

PCC Evidence — CLI

Browse, inspect, and understand evidence bundles and verification protocols for PCC jobs.

When to use

"Show evidence for job X"
"List verification protocols"
"Check the evidence bundle for bundle-abc123"
"What evidence was submitted for the HPLC run?"
"Is the ZK proof ready?"
"Show all evidence bundles"
"What protocols are available for Tier 2?"
"Verify the evidence for milestone 2"

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

Evidence List — All Evidence Bundles

node packages/mcp-server/dist/cli.js evidence list

Lists all evidence bundles across all jobs. Each entry shows: bundle ID, associated job ID, milestone number, IPFS CID, encryption status, ZK proof status, Bittensor verification score, and creation timestamp. Use this to get a broad view of evidence state across the network.

Filter by job:

node packages/mcp-server/dist/cli.js evidence list --job J-0047

Evidence Get — Specific Bundle Details

node packages/mcp-server/dist/cli.js evidence get <bundleId>

Returns full details for a specific evidence bundle. Output includes:

Bundle ID and associated job/milestone
Encryption: Lit Protocol AES-256-GCM status, access control conditions
IPFS CID: Content-addressed storage path (immutable once stored)
Evidence events: List of collected data points (measurements, sensor readings, photos, certificates)
ZK proof: Generated? Verified? Proof ID if available
Bittensor verification: Miner consensus score (0-1), number of miners that participated, individual miner votes
Evaluator attestation: If a third-party evaluator attested, shows their DID, score, and findings

Example:

node packages/mcp-server/dist/cli.js evidence get bafkreiabcdef1234

Protocols List — Protocol Templates

node packages/mcp-server/dist/cli.js protocols list

Lists all protocol templates (multi-step workflow templates used as evidence collection blueprints). Each protocol defines: step sequence, what data to collect at each step, acceptance criteria, and assurance tier compatibility. Use this to understand what evidence patterns exist before building a contract.

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

2mo ago First seen · 123 lines · 0 tokens per session scan A 7f23eadf24c1

Subscribe to this mod's changes

pcc-evidence is a command published in the GitHub repository global-mysterysnailrevolution/physical-capability-cloud (5 stars, last pushed 7mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 1,274 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.

Research

pcc-evidence next to 6 commands from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
pcc-evidenceglobal-mysterysnailrevolution/physical-capability-cloud	Command	5	7mo ago	Apache-2.0	A	0	Claude Code
checklistgithub/spec-kit	Command	148k	yesterday	MIT	A	13	Claude Code
clarifygithub/spec-kit	Command	148k	yesterday	MIT	A	27	Claude Code
specifygithub/spec-kit	Command	148k	yesterday	MIT	A	13	Claude Code
analyzegithub/spec-kit	Command	148k	yesterday	MIT	A	26	Claude Code
convergegithub/spec-kit	Command	148k	yesterday	MIT	A	35	Claude Code
implementgithub/spec-kit	Command	148k	yesterday	MIT	A	14	Claude Code

physical-capability-cloud: Command for Claude Code