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-ui-capability-card.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-ui-capability-card)<a href="https://agentmods.dev/commands/global-mysterysnailrevolution/physical-capability-cloud/pcc-ui-capability-card"><img src="https://agentmods.dev/badge/commands/global-mysterysnailrevolution/physical-capability-cloud/pcc-ui-capability-card/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-ui-capability-card"><img src="https://agentmods.dev/badge/commands/global-mysterysnailrevolution/physical-capability-cloud/pcc-ui-capability-card.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.00370 |
| Opus 5 | $0.00000 | $0.00185 |
| Sonnet 5 | $0.00000 | $0.00074 |
| Haiku 4.5 | $0.00000 | $0.00037 |
Grade A, and why
pcc-ui-capability-card 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-ui-capability-card — 100% identical, 0 lines differ
What it actually says
Generate a PCC Capability Card React component using the @pcc/ui Solarpunk design system.
Pattern source: Virtuals agent listing cards + 8004scan agent browser
Component Spec
Generate a CapabilityCard component in packages/ui/src/discovery/CapabilityCard.tsx with:
- Visual: GlassPanel with BorderBeam accent, dark bg (gray-900/80), teal/green glow
- Header: Capability name (bold) + type badge (GlowBadge, teal) + online indicator (green pulse dot)
- Body: Operator/kernel name, location, key specs as labeled chips
- Metrics row: Assurance tier (TierBadge), quality score, price + SLA
- Footer: "Get Quote" CTA button (green gradient) + mini reputation sparkline
- Props:
capability: { name, type, operator, location, specs, price, sla, tier, score, trend[] },onQuote: () => void
Design Tokens
- Background:
bg-gray-900/80 - Border:
border-teal-500/20with<BorderBeam size={100} duration={8} /> - Badge colors: tier=TierBadge, quality≥90=green, quality≥75=gold, else=red
- Text: primary
text-white/80, secondarytext-white/40, mono valuesfont-mono - Hover:
hover:border-teal-400/40 transition-all
Imports
import { GlassPanel, GlowBadge, TierBadge, BorderBeam, PulseIndicator } from "@pcc/ui";
import { motion } from "motion/react";
Use existing components. Follow the patterns in packages/ui/src/primitives/.
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 · 30 lines · 0 tokens per session scan A d1487de4473e
pcc-ui-capability-card 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 370 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
design-import
Scaffolds React components from a Claude Design handoff bundle and stops at files on disk: no stories, no tests, no pull request. Use when handed a claude.ai/design URL or a local bundle file; when that same scaffold should carry on through test generation, browser verification and an opened PR, run /ork:design-ship…
setup
Add Tailwind CSS v4 and shadcn/ui to an existing React/Vite project.
figma-component-builder
Automate conversion of Figma designs into React/TypeScript components and supporting artifacts for a selected project scope. Uses a Figma MCP server (or connector) to fetch design context and a browser automation tool to verify produced components against a running dev server. Follows the conventions described in the…
visual
Frontend and UI specialist. Use for React/Vue/Svelte components, CSS/Tailwind styling, accessibility, responsive design, and visual implementation tasks.
to-code
A command that converts a selected design node into React and Tailwind code. React is a JavaScript interface library, and Tailwind is a CSS styling toolkit.
checklist
Generate a custom checklist for the current feature based on user requirements.