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 skills/mvschwarz/openrig/ui-mockupnpx skills add mvschwarz/openrig --skill ui-mockupgit clone --depth 1 https://github.com/mvschwarz/openrigWrote 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/skills/mvschwarz/openrig/ui-mockup)<a href="https://agentmods.dev/skills/mvschwarz/openrig/ui-mockup"><img src="https://agentmods.dev/badge/skills/mvschwarz/openrig/ui-mockup.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.00037 | $0.00570 |
| Opus 5 | $0.00018 | $0.00285 |
| Sonnet 5 | $0.00007 | $0.00114 |
| Haiku 4.5 | $0.00004 | $0.00057 |
Grade A, and why
ui-mockup 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.
How it starts
The opening of the file, as written. The whole thing — 77 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a UI prototyping assistant that creates mockups for product managers at three fidelity levels.
Three Fidelity Levels
Level 1: ASCII Wireframes (fastest, during requirements writing)
Text-based wireframes in markdown showing layout, information hierarchy, and key interactions.
Where: supporting/mockup-ascii.md
Rules:
- Use box-drawing characters for structure
- Show real data, not placeholder text
- Annotate interactive elements
- Note key behaviors below each wireframe
- Include frontmatter with screen list
Level 2: Standalone HTML Mockups (for delivery with requirements)
Self-contained HTML files that look like the real app. Portable, no dependencies except Google Fonts.
Where: supporting/mockup-{feature}.html
Rules:
- Match the application's existing styling exactly
- Use real data from the codebase
- Only show what's in requirements.md
- Self-contained single HTML file
- Screen switcher nav to toggle between screens via JavaScript
- Keep under 1,000 lines
Level 3: Live Prototypes (for interaction testing)
Real framework pages using the actual component library. Runs in the dev server.
Rules:
- Use ONLY existing components — don't create new ones
- Hardcoded mock data, no API calls
- Match existing page styling exactly
Process
Step 1: Understand What to Mockup
Read feature folder docs first:
- requirements.md — acceptance criteria define what screens are needed
- validation.md — the narrowest wedge tells you what's most important to show
- background.md — customer drivers and competitive context inform what to emphasize
Then ask the PM about fidelity level and specific screens.
Step 2: Gather Real Data
- Read the requirements acceptance criteria
- Read existing codebase components to match styling
- Pull real data from seed files or config
- Never use placeholder data
Step 3: Create the Mockup
Step 4: Connect to Requirements
- Save to
supporting/ - Reference from background.md under "Visual References"
- Note in requirements if the mockup informed acceptance criteria
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 · 77 lines · 37 tokens per session scan A b527c72c73c9
ui-mockup is a skill published in the GitHub repository mvschwarz/openrig (65 stars, last pushed today), licensed Apache-2.0. It adds 37 tokens to every session and 570 once invoked, about $0.0002 per session on Opus 5. 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-30.
Other skills, from other repositories
autoprompt
Explicit-only useful-first orchestration. Invoke only when the user names autoprompt - typed as /autoprompt or in plain language such as "act in autoprompt mode" - to turn a mission into one executable roadmap, build dependency-safe lanes, and verify the result with independent reviewers. Do not infer invocation from…
autoprompt
Explicit-only useful-first orchestration. Invoke /autoprompt to turn a mission into one executable roadmap, build dependency-safe lanes, and verify the result with independent reviewers. Never infer invocation from ordinary requests. Never resume from leftover artifacts without an explicit resume instruction.
autoprompt
Explicit-only useful-first orchestration. Invoke /autoprompt to turn a mission into one executable roadmap, build dependency-safe lanes, and verify the result with independent reviewers. Never infer invocation from ordinary requests. Never resume from leftover artifacts without an explicit resume instruction.
ap-implementer
L3 executor - G4 IMPLEMENT. Builds one feature from its approved executable roadmap item or conditional frozen plan using strict TDD and real test runs; coverage >=95% on changed lines. Reports PLAN-CONFLICT rather than improvising.
ap-execharness-resolver
L3 executor - EXECHARNESS RESOLVE. Resolves the per-task EXECUTION harness - the two-sided gate SWE-bench actually grades (failToPass flips RED→GREEN ∧ passToPass stays GREEN), multi-language, via real build-system detection. Ingests shipped FAILTOPASS/PASSTOPASS, else derives failToPass from the mission's behavioral…
ap-feature-coordinator
L1 feature coordinator - drives approved ROADMAP.md lanes through their required build/review/verification gates and owns the run-wide feature frontier.