use-dom

use-dom is a skill for Claude Code, Codex from Intelligent-Internet/ii-agent. It costs 32 tokens per session (2,388 once invoked), scanned A, original, Apache-2.0.

A guide for using Expo DOM components, which run browser-based web code inside a webview on phones and directly on the web. Expo is a framework for building apps with React Native.

In plain words
What is it for?
Use it when adding charts, editors, rich text, browser embeds, canvas graphics, or existing React web code to an Expo app.
Why use it?
It lets you reuse web components and web-only libraries without rewriting them for native platforms.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Needs its repository: it reads a path above its own folder, which exists only inside the repository. The line is const logo = require("../assets/logo.png");.

Good fit Use it when adding charts, editors, rich text, browser embeds, canvas graphics, or existing React web code to an Expo app.

Compare 6 skills from other repositories ↓
About the project

II-Agent is an open-source framework and AI agent for building applications, conducting research, and automating workflows from natural-language prompts. Developers, research teams, and enterprises use it to create mobile apps, websites, illustrated books, media, research outputs, and integrations with external services. The catalogue skills and instructions provide workflows and integrations for using II-Agent.

Intelligent-Internet/ii-agent · 3,382 stars · on GitHub · ii.inc

Install

Getting it into your agent

It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.

Clone the repo
git clone --depth 1 https://github.com/Intelligent-Internet/ii-agent
agentmods
npx agentmods add skills/intelligent-internet/ii-agent/expo-use-dom

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for use-dom

README.md
[![agentmods](https://agentmods.dev/badge/skills/intelligent-internet/ii-agent/expo-use-dom/github.svg)](https://agentmods.dev/skills/intelligent-internet/ii-agent/expo-use-dom)
Your own site
<a href="https://agentmods.dev/skills/intelligent-internet/ii-agent/expo-use-dom"><img src="https://agentmods.dev/badge/skills/intelligent-internet/ii-agent/expo-use-dom/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.

agentmods 80×15 button for use-dom

Your own site · 80×15
<a href="https://agentmods.dev/skills/intelligent-internet/ii-agent/expo-use-dom"><img src="https://agentmods.dev/badge/skills/intelligent-internet/ii-agent/expo-use-dom.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 32 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,388 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00032 $0.02388
Opus 5 $0.00016 $0.01194
Sonnet 5 $0.00006 $0.00478
Haiku 4.5 $0.00003 $0.00239

Measured 12d ago against content hash 7041bb26db02, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

use-dom 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 12d 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.

Origin

Copies of this mod

8 near-identical copies found in the catalogue:

  • use-dom — 100% identical, 3 lines differ
  • use-dom — 100% identical, 0 lines differ
  • use-dom — 100% identical, 0 lines differ
  • use-dom — 100% identical, 0 lines differ
  • use-dom — 100% identical, 0 lines differ
  • use-dom — 100% identical, 0 lines differ
  • expo-use-dom-v55 — 86% identical, 12 lines differ
  • expo-dom — 84% identical, 12 lines differ
src/ii_agent/agents/skills/builtin/expo-use-dom/SKILL.md · 418 lines

How it starts

The opening of the file, as written. The whole thing — 418 lines — stays where its author put it; the contents beside it link to each section on GitHub.

What are DOM Components?

DOM components allow web code to run verbatim in a webview on native platforms while rendering as-is on web. This enables using web-only libraries like recharts, react-syntax-highlighter, or any React web library in your Expo app without modification.

When to Use DOM Components

Use DOM components when you need:

  • Web-only libraries — Charts (recharts, chart.js), syntax highlighters, rich text editors, or any library that depends on DOM APIs
  • Migrating web code — Bring existing React web components to native without rewriting
  • Complex HTML/CSS layouts — When CSS features aren't available in React Native
  • iframes or embeds — Embedding external content that requires a browser context
  • Canvas or WebGL — Web graphics APIs not available natively

When NOT to Use DOM Components

Avoid DOM components when:

  • Native performance is critical — Webviews add overhead
  • Simple UI — React Native components are more efficient for basic layouts
  • Deep native integration — Use local modules instead for native APIs
  • Layout routes_layout files cannot be DOM components

Basic DOM Component

Create a new file with the 'use dom'; directive at the top:

// components/WebChart.tsx
"use dom";

export default function WebChart({
  data,
}: {
  data: number[];
  dom: import("expo/dom").DOMProps;
}) {
  return (
    <div style={{ padding: 20 }}>
      <h2>Chart Data</h2>
      <ul>
        {data.map((value, i) => (
          <li key={i}>{value}</li>
        ))}
      </ul>
    </div>
  );
}

Rules for DOM Components

  1. Must have 'use dom'; directive at the top of the file
  2. Single default export — One React component per file
  3. Own file — Cannot be defined inline or combined with native components
  4. Serializable props only — Strings, numbers, booleans, arrays, plain objects
  5. Include CSS in the component file — DOM components run in isolated context

The dom Prop

Read the full file on GitHub · 418 lines

Changes

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.

  1. 12d ago First seen · 418 lines · 32 tokens per session scan A 7041bb26db02

Subscribe to this mod's changes

use-dom is a skill published in the GitHub repository Intelligent-Internet/ii-agent (3,382 stars, last pushed 26d ago), licensed Apache-2.0. It adds 32 tokens to every session and 2,388 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.

Related

Other skills, from other repositories

stream-react-native

Builds, integrates, migrates, and audits Stream Chat, Stream Video, and Stream Feeds in React Native CLI and Expo apps. Use when scaffolding a new RN/Expo Chat, Video, or Feeds app, adding Stream to an existing RN app, upgrading a Stream SDK version (stream-chat-react-native v8 to v9, Feeds v2 to v3), migrating from…

GetStream/agent-skills · 238 tokens

rn-best-practices

This skill should be used when writing or reviewing React Native / Expo code — before writing list rendering, animations, data fetching, component APIs, navigation, or image/media UI — and when asked to "review best practices", "check performance", "optimize renders", "review list rendering", "check animation…

Lykhoyda/rn-dev-agent · 98 tokens

rn-feature-dev

Explicit Codex workflow: Guided feature development for React Native — explore codebase, design architecture, implement, verify live on device, and review quality.

Lykhoyda/rn-dev-agent · 34 tokens

agent-spec-mobile-react-native

Agent skill for spec-mobile-react-native - invoke with $agent-spec-mobile-react-native.

ruvnet/ruflo · 22 tokens

langbot-dev

Develop, build, and debug the LangBot core backend and web frontend. Use when working inside the LangBot repository — backend (Python/Quart, src/langbot/pkg), the Vite/React web UI, HTTP API controllers/services, Alembic migrations, or the MCP server. Covers the dev environment (uv, pnpm), repo layout, the API auth…

langbot-app/LangBot · 136 tokens

web-design

Penguin visual language for generated web pages and app UIs — GitHub-style simplicity with a single blue accent, light and pure-black dark themes, design tokens, component and chat-interface recipes, plus an opt-in warm paper editorial theme.

Prism-Shadow/penguin-harness · 51 tokens