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-onboard-prompt.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-onboard-prompt)<a href="https://agentmods.dev/commands/lamasu/physical-capability-cloud/pcc-ui-onboard-prompt"><img src="https://agentmods.dev/badge/commands/lamasu/physical-capability-cloud/pcc-ui-onboard-prompt.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.00368 |
| Opus 5 | $0.00000 | $0.00184 |
| Sonnet 5 | $0.00000 | $0.00074 |
| Haiku 4.5 | $0.00000 | $0.00037 |
Grade A, and why
pcc-ui-onboard-prompt 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-onboard-prompt — 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 Onboarding page with prompt-to-build capability registration.
Pattern source: Pakt "Prompt-to-Build" + PCC existing 7-step wizard
Component Spec
Add a PromptOnboard component to the onboarding flow:
- Large text input: "Describe your equipment and what it can do..."
- AI interpretation panel: Side-by-side view showing:
- Left: User's natural language description
- Right: AI-inferred configuration (capability type, specs, pricing, evidence requirements)
- Edit mode: User can adjust any AI-inferred value
- Configuration preview:
- Kernel name and description
- Capability type badge
- Specifications table
- Suggested pricing with market comparison
- Required evidence types for chosen assurance tier
- ERC-8004 Agent Registration File preview (JSON viewer)
- Registration flow: Description → Config → Pricing → Register → Live
- Progress indicator: 5 steps with active step highlighted
Example prompts to handle
- "I have a Shimadzu HPLC with UV detector, we do pharma purity analysis in 4 hours"
- "Haas VF-2 CNC mill, aluminum and steel, ±0.01mm tolerance, Bay Area"
- "Prusa i3 MK3S+ for PLA/PETG printing, 24h turnaround, hobby level"
Design
- Prompt input: Full-width, 3-line textarea, GlassPanel, green border on focus
- Side-by-side: CSS grid 1fr 1fr, left with user text, right with structured config
- Config items: Key-value rows in GlassPanel, editable on click
- JSON preview: Monospace, syntax-highlighted, collapsible
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 · 34 lines · 0 tokens per session scan A d17e98498d53
pcc-ui-onboard-prompt 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 368 tokens. A static security scan graded it A with 0 findings. It is 100% identical to pcc-ui-onboard-prompt, differing in 0 lines, and is treated as a copy.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.