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/othmanadi/openui-forge/openui-forge-elixirnpx skills add OthmanAdi/openui-forge --skill openui-forge-elixirgit clone --depth 1 https://github.com/OthmanAdi/openui-forgeWhat 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.00028 | $0.02620 |
| Opus 5 | $0.00014 | $0.01310 |
| Sonnet 5 | $0.00006 | $0.00524 |
| Haiku 4.5 | $0.00003 | $0.00262 |
Grade A, and why
openui-forge-elixir 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.
How it starts
The opening of the file, as written. The whole thing — 267 lines — stays where its author put it; the contents beside it link to each section on GitHub.
OpenUI Forge — Elixir
Build generative UI apps with a React frontend + Elixir Phoenix backend. Streams OpenAI API responses directly to the browser as SSE using Plug.Conn.send_chunked/2 and the Req HTTP client's streaming :into collector.
Activation Triggers
- "openui elixir", "openui phoenix", "openui elixir backend"
- "generative ui elixir", "elixir streaming ui backend", "phoenix sse openui"
Prerequisites
- Node.js >= 22 (24 LTS recommended) + React >= 18.3.1 (19+ recommended) (frontend)
- Elixir >= 1.15 with Erlang/OTP 25+ (Phoenix 1.8 baseline)
- Phoenix ~> 1.8 (current stable; 1.8.8 as of June 2026)
OPENAI_API_KEYenvironment variable set
Quick Start
- Create the React frontend and install OpenUI deps:
npm install @openuidev/react-ui @openuidev/react-headless @openuidev/react-lang lucide-react zod
- Generate the system prompt into the Phoenix app's
priv/:
npx @openuidev/cli generate ./src/lib/library.ts --out backend/priv/system-prompt.txt
- Create the Phoenix backend (see Full Code below)
- Run:
mix deps.get && mix phx.serveron:4000, frontend on:3000
Full Code
Backend: backend/mix.exs (deps)
defp deps do
[
{:phoenix, "~> 1.8.0"},
{:bandit, "~> 1.0"}, # HTTP server (Phoenix 1.8 default)
{:jason, "~> 1.4"}, # JSON encode/decode
{:req, "~> 0.6"}, # HTTP client with streaming :into (v0.6.2+)
{:cors_plug, "~> 3.0"} # explicit-origin CORS
]
end
Backend: load the system prompt once at startup
Read priv/system-prompt.txt a single time and cache it in :persistent_term. Call OpenuiBackend.load_system_prompt!/0 from your Application.start/2 callback before the endpoint child starts.
# lib/openui_backend.ex
defmodule OpenuiBackend do
@key {__MODULE__, :system_prompt}
def load_system_prompt! do
path = Application.app_dir(:openui_backend, "priv/system-prompt.txt")
case File.read(path) do
{:ok, contents} ->
:persistent_term.put(@key, contents)
:ok
{:error, reason} ->
raise "failed to read #{path}: #{:file.format_error(reason)}"
end
end
def system_prompt, do: :persistent_term.get(@key)
end
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 · 267 lines · 28 tokens per session scan A bf39cc096c44
openui-forge-elixir is a skill published in the GitHub repository OthmanAdi/openui-forge (22 stars, last pushed 1mo ago), licensed MIT. It adds 28 tokens to every session and 2,620 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 skills, from other repositories
release-notes
Draft concise release notes.
openbot-data-access
Governs how the OpenBot browser app reads and writes server data — every request goes through client in app/src/lib/client.ts, every read is a queryOptions factory in app/src/lib/ /queries.ts, every write is a mutationOptions factory in app/src/lib/ /mutations.ts, and components consume them through…
sq-site-dependabot
Reviews, validates, and safely merges Dependabot pull requests for the sq.io site (site/, Bun lockfile). Use when clearing site dependency PRs, triaging Dependabot failures, or checking Lighthouse impact before merge.
sq
Guides use of the sq CLI to query SQL databases and tabular files with SLQ (sq's jq-like query language) or native SQL, manage sources, choose output formats, and run inspect, diff, and table commands. Use when the user mentions sq, SLQ, wrangling CSV/Excel/JSON/DB data, cross-source joins, or command-line data…
dd-code-generation
Use pup CLI for immediate Datadog operations or generate code for integration into applications.
drt-analyze
Analyze DRT cluster health for a given time range. Reconstructs the operations timeline, checks CockroachDB metrics (availability, latency, storage, changefeeds, jobs, goroutines, admission control, LSM, KV prober) and logs for anomalies, correlates findings with disruptive operations to distinguish expected…