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-leaderboardgit 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-leaderboard)<a href="https://agentmods.dev/commands/lamasu/physical-capability-cloud/pcc-ui-leaderboard"><img src="https://agentmods.dev/badge/commands/lamasu/physical-capability-cloud/pcc-ui-leaderboard.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.1 | $0.00000 | $0.00272 |
| Opus 5 | $0.00000 | $0.00136 |
| Sonnet 5 | $0.00000 | $0.00054 |
| Haiku 4.5 | $0.00000 | $0.00027 |
Grade A, and why
pcc-ui-leaderboard 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 5d 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-leaderboard — 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 Operator Leaderboard React component.
Pattern source: 8004scan agent leaderboard + Virtuals top agents by aGDP
Component Spec
Generate a OperatorLeaderboard component in packages/ui/src/kernel/OperatorLeaderboard.tsx with:
- Sortable table: Rank, operator name, total revenue, jobs completed, success rate, reputation score
- Filters: Capability type dropdown, location, assurance tier minimum
- Per-row: 7d sparkline chart (tiny bar chart), online status (PulseIndicator)
- Click: Navigate to operator detail page
- Header KPIs: Total operators, total revenue, avg success rate (AnimatedNumber)
- Props:
operators: Array<{ rank, name, kernelId, revenue, jobCount, successRate, reputationScore, trend[], online, capabilities[] }>
Design
- Table:
w-full text-xs, headertext-white/30 border-b border-white/[0.06] - Rows:
hover:bg-white/[0.02], alternating subtle bg - Revenue:
text-green-400 font-mono - Sparklines: 7 tiny bars,
bg-green-400/60, max height 16px - Sort indicators: arrow up/down icons in headers
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.
- 5d ago First seen · 22 lines · 0 tokens per session scan A 10b5b669cc16
pcc-ui-leaderboard 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 272 tokens. A static security scan graded it A with 0 findings. It is 100% identical to pcc-ui-leaderboard, 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.
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.