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-ui-capability-cardgit 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-capability-card)<a href="https://agentmods.dev/commands/lamasu/physical-capability-cloud/pcc-ui-capability-card"><img src="https://agentmods.dev/badge/commands/lamasu/physical-capability-cloud/pcc-ui-capability-card.svg" alt="Measured on agentmods" 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 | $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 4d 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-capability-card — 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 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.
- 4d ago First seen · 30 lines · 0 tokens per session scan A d1487de4473e
pcc-ui-capability-card is a command published in the GitHub repository LamaSu/physical-capability-cloud (1 stars, last pushed 2d 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. It is 100% identical to pcc-ui-capability-card, differing in 0 lines, and is treated as a copy.
Other commands, from other repositories
frontend
Injects context of all relevant cli files.
component
Scaffold a new React component grounded in the paper-mono primitives. Requires explicit kind or a nearest-existing-component match. No empty divs, no speculative scaffolding.
replan-remaining-work
Command "replan-remaining-work" from udecode/plate, covering command: re-plan remaining work, when to run, hard rule, invocation and refresh afterward.
speckit-gaia-plan-close
Close a plan after implementation+merge. Offers wiki-promote for the plan's consolidated SUMMARY.md, cold-consolidates an out-of-band merge, then early-reaps the local plan folder once cost is represented in cost.jsonl.
review-arch
Review the current branch for code quality, TypeScript, and React/Next.js patterns. Supports whole-branch review or scoped review by path, feature, or base branch.
speckit.clarify
This project uses the GAIA preset. Bare /speckit-clarify is not the clarify path here: core clarify writes an off-shape artifact (a ## Clarifications / ### Session block with five-word answers) and carries a question cap GAIA does not use. Run /gaia-spec instead — it drives GAIA's coverage-based Socratic clarify loop…