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/othmanadi/openui-forge/openui-scaffoldgit clone --depth 1 https://github.com/OthmanAdi/openui-forgeWrote 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/othmanadi/openui-forge/openui-scaffold)<a href="https://agentmods.dev/commands/othmanadi/openui-forge/openui-scaffold"><img src="https://agentmods.dev/badge/commands/othmanadi/openui-forge/openui-scaffold.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 | $0.00015 | $0.00570 |
| Opus 5 | $0.00008 | $0.00285 |
| Sonnet 5 | $0.00003 | $0.00114 |
| Haiku 4.5 | $0.00002 | $0.00057 |
Grade A, and why
openui-scaffold 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 3d 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.
What it actually says
Trigger the OpenUI scaffolding workflow. Follow the decision tree from SKILL.md exactly.
Step 1 — Detect project state:
- Check if a package.json exists in the current directory
- If yes, detect the framework by checking for next.config., vite.config., or neither
- If no package.json exists, check if this is a non-JS project (look for requirements.txt, go.mod, Cargo.toml)
Step 2 — Follow the scaffold decision tree:
No existing project detected:
- Run
npx @openuidev/cli@latest create --name ${PROJECT_NAME}(ask the user for a project name) - Wait for scaffold to complete
- Inform the user to run
/openui:integratenext
Existing Next.js project:
- Install dependencies:
npm install @openuidev/react-ui @openuidev/react-headless @openuidev/react-lang @modelcontextprotocol/sdk lucide-react zod - Add the CSS import to the root layout file (app/layout.tsx or similar):
import "@openuidev/react-ui/components.css"; - Create a component library file using
templates/library.ts.template— or ask the user if they want to use the built-inopenuiChatLibraryfrom@openuidev/react-ui/genui-lib(chat-aware) oropenuiLibrary(component-only) - Recommend running
/openui:integratenext
Existing Vite + React project:
- Same dependencies as Next.js
- Add CSS imports to the main entry file (main.tsx or App.tsx)
- Create a component library file using
templates/library.ts.template - Note: A proxy to the backend will need to be configured in vite.config.ts during integration
- Recommend running
/openui:integratenext
Non-JS backend (Python / Go / Rust):
- Create a React frontend (ask: Next.js or Vite?) and install OpenUI deps there
- Create a component library in the frontend using
templates/library.ts.template - Run
npx @openuidev/cli generate ./src/lib/library.ts --out system-prompt.txtto pre-generate the system prompt - Copy system-prompt.txt to the backend service directory
- Note: The backend handler will be created during
/openui:integrate - Recommend running
/openui:integratenext
After scaffolding, always run /openui to verify the project state.
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.
- 3d ago First seen · 45 lines · 15 tokens per session scan A 0498ffebf092
openui-scaffold is a command published in the GitHub repository OthmanAdi/openui-forge (22 stars, last pushed 1mo ago), licensed MIT. It adds 15 tokens to every session and 570 once invoked, about $0.0001 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 commands, from other repositories
billing
This API allows you to query billing related objects.
object
Command "object" from scaleway/scaleway-cli, covering documentation for scw object, manage s3 buckets, create an s3 bucket, delete an s3 bucket and get information about an s3 bucket.
search
Command "search" from scaleway/scaleway-cli, covering documentation for scw search, resource search commands and search api.
account
This API allows you to manage your Scaleway Projects.
alias
This namespace allows you to manage your aliases Aliases are store in cli config file, Default path for this configuration file is based on the following priority order.
feedback
Command "feedback" from scaleway/scaleway-cli, covering documentation for scw feedback, send a bug-report and send a feature request.