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-revenue-dashboard.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-revenue-dashboard)<a href="https://agentmods.dev/commands/lamasu/physical-capability-cloud/pcc-ui-revenue-dashboard"><img src="https://agentmods.dev/badge/commands/lamasu/physical-capability-cloud/pcc-ui-revenue-dashboard/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-revenue-dashboard"><img src="https://agentmods.dev/badge/commands/lamasu/physical-capability-cloud/pcc-ui-revenue-dashboard.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.00227 |
| Opus 5 | $0.00000 | $0.00113 |
| Sonnet 5 | $0.00000 | $0.00045 |
| Haiku 4.5 | $0.00000 | $0.00023 |
Grade A, and why
pcc-ui-revenue-dashboard 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 8d 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-revenue-dashboard — 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 update the PCC Revenue Dashboard page at apps/dashboard/src/pages/RevenueDashboardPage.tsx.
Pattern source: Virtuals performance dashboard (aGDP metrics) + Pakt Command Center (4 charts)
The page already exists — use this skill to add features, fix issues, or regenerate sections.
Component Structure
- 4 KPI cards: Total Revenue, Active Jobs, Success Rate, Reputation Score (AnimatedNumber + TierBadge)
- Revenue line chart: Recharts with period selector (30d/90d/1y)
- Capability performance table: Name, revenue, jobs, avg price, quality score, 7d sparkline
- Active escrows: Cards with milestone progress bars
- DePIN rewards: Epoch info, rank, points, next claim
- Reviews: Sortable (all/highest/lowest), star rating, text, author address
Data source
Mock data in apps/dashboard/src/api/mock-revenue-data.ts. In production: gateway API routes.
Design tokens
Follow existing Solarpunk palette: teal/cyan accents, GlassPanel, GlowBadge, dark backgrounds.
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.
- 8d ago First seen · 20 lines · 0 tokens per session scan A f2361570a65c
pcc-ui-revenue-dashboard is a command published in the GitHub repository LamaSu/physical-capability-cloud (1 stars, last pushed today), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 227 tokens. A static security scan graded it A with 0 findings. It is 100% identical to pcc-ui-revenue-dashboard, differing in 0 lines, and is treated as a copy.
Other commands, from other repositories
prototype-loop
Enter leveraged-prototype focus mode — focus marker plus normal watch/rebuild loop for visual-parity work and batch upstream framework gap-fixes.
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.
a11y-audit-react
Identify accessibility violations in React components and provide actionable remediation aligned with WCAG 2.2 Level AA. This is the guided audit workflow that applies the standards defined in the a11y-automation and react-components rules.
create-variant
Add a new variant to an existing shadcn/ui component.
react-build
Fix React build failures (Vite, webpack, Next.js, CRA, Parcel, esbuild, Bun) incrementally — JSX/TSX compile errors, hydration mismatches, server/client component boundary failures, missing types. Invokes the react-build-resolver agent for minimal, surgical fixes.
next-upgrade
Structured workflow for upgrading Next.js applications across major versions. Use when migrating a Next.js project from one major version to another (e.g., 13 to 14, 14 to 15, 15 to 16). Covers codemod automation, breaking change detection, incremental migration paths, and post-upgrade validation.