OpenRig is a software harness that coordinates Claude Code and Codex coding agents as one system, with agent teams defined in YAML and launched together. It is for organizing persistent teams of coding agents that can delegate work to specialists and return results or decisions. The catalogue lists 53 skills and one plugin as add-ons for OpenRig.
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 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/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/skills/mvschwarz/openrig/ui-mockup"><img src="https://agentmods.dev/badge/skills/mvschwarz/openrig/ui-mockup.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.5 | $0.00015 | $0.00228 |
| Sonnet 5.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 1mo 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 SPEC.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:
- SPEC.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.
- 1mo ago Changed a597fad7dcde
- 1mo ago First seen · 77 lines · 37 tokens per session scan A b527c72c73c9
ui-mockup is a skill published in the GitHub repository mvschwarz/openrig (8,062 stars, last pushed today), licensed Apache-2.0. It adds 37 tokens to every session and 570 once invoked, about $0.0001 per session on Opus 5.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
desktop-brand-builder
Generate a branded Qwen Code desktop package from the Tauri desktop shell using a minimal brandId and logo. Use when the user wants a custom, white-label, or rebranded desktop client, installer, DMG/EXE/AppImage/deb, or one-click brand build on top of packages/desktop.
dataviz
Design guidance for charts, graphs, dashboards, maps, and data visualizations, including a local palette validator.
frontend-design
Produce intentional, responsive, accessible UI work and perform visual QA instead of generic component assembly.
metis
A task-routing and checking workflow for explicitly requested Metis work. It assigns work to defined roles, records checks, and limits recovery when something fails.
accessibility
Use when making a web UI conform to WCAG 2.2 Level AA — axe-core or Lighthouse a11y violations, keyboard operability, focus management, ARIA roles/names/live regions, contrast, tap-target size. NOT palette or visual intent (that is design), NOT test-runner setup (that is testing-web), NOT LCP/page-speed (that is…
brand-identity
Use when a project needs its visual foundation built or consolidated into one system: logo brief, color system in HEX/RGB/CMYK/OKLCH with proven AA contrast, type system, usage rules, and an exported W3C design-tokens.json that later skills consume. NOT the applied UI pixels (that is design), NOT the words or tone…