Borrowing it
Nothing to install: this file belongs to LamaSu/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/LamaSu/physical-capability-cloud/master/.claude/commands/pcc-ui-evidence-explorer.mdgit clone --depth 1 https://github.com/LamaSu/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/lamasu/physical-capability-cloud/pcc-ui-evidence-explorer)<a href="https://agentmods.dev/commands/lamasu/physical-capability-cloud/pcc-ui-evidence-explorer"><img src="https://agentmods.dev/badge/commands/lamasu/physical-capability-cloud/pcc-ui-evidence-explorer/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/lamasu/physical-capability-cloud/pcc-ui-evidence-explorer"><img src="https://agentmods.dev/badge/commands/lamasu/physical-capability-cloud/pcc-ui-evidence-explorer.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.00331 |
| Opus 5.5 | $0.00000 | $0.00132 |
| Sonnet 5.5 | $0.00000 | $0.00066 |
| Haiku 4.5 | $0.00000 | $0.00033 |
Grade A, and why
pcc-ui-evidence-explorer 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.
This is a copy
100% identical to pcc-ui-evidence-explorer — 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.
What it actually says
Generate or enhance the PCC Evidence Explorer with evaluator attestation support.
Pattern source: PCC existing /evidence + Virtuals evaluator pattern + 8004scan transaction feed
Enhancements to existing EvidenceExplorerPage
- Evidence cards: Each bundle as a GlassPanel card with:
- Encryption status indicator (locked/unlocked icon + GlowBadge)
- IPFS CID (IPFSLink component)
- Evidence event count
- ZK proof status badge (verified/pending/none)
- Bittensor consensus score (0-1 with color coding)
- NEW: Evaluator attestation badge (who verified, score, verdict)
- Click to decrypt: Lit Protocol access control check → show decrypted evidence
- Evaluator section: When evaluator has signed off:
- Evaluator identity (ERC-8004 agent ID)
- Verdict: pass/conditional/fail with color
- Score: 0-100
- Findings: Expandable list with severity badges (critical=red, major=gold, minor=gray)
- Signed attestation VC hash
- Transaction feed: Chronological view of all evidence submissions with from/to tracking
- Filters: By job, capability type, verification status, evaluator
Design
- Cards: GlassPanel with encryption lock icon top-right
- Decrypt button: Glowing green border, "Decrypt" label
- Evaluator badge: GlowBadge with verdict color, evaluator name truncated
- Findings: Collapsible list, severity-colored left border
- Feed: Vertical timeline with timestamps and action types
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 · 30 lines · 0 tokens per session scan A 667f69e052d9
pcc-ui-evidence-explorer is a command published in the GitHub repository LamaSu/physical-capability-cloud (3 stars, last pushed 5d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 331 tokens. A static security scan graded it A with 0 findings. It is 100% identical to pcc-ui-evidence-explorer, differing in 0 lines, and is treated as a copy.
pcc-ui-evidence-explorer compared with commands from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| pcc-ui-evidence-explorerLamaSu/physical-capability-cloud | Command | 3 | 5d 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 |