A development guide for an Xray Config UI Editor, a web app for editing Xray-core network configuration. It covers the React interface, its stored data, configuration logic, and Remnawave integration.

Use it to modify the editor interface, update configuration state and Xray settings, change the visual topology view or JSON editor, and connect changes with Remnawave.

It gives the coding agent project-specific rules and locations, reducing guesswork when changing the editor or its configuration handling.

xray-ui-dev — Skill by bropines

Install

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.

agentmods

npx agentmods add skills/bropines/xray-config-ui-editor/xray-ui-dev

Any agent

npx skills add bropines/xray-config-ui-editor --skill xray-ui-dev

Clone the repo

git clone --depth 1 https://github.com/bropines/xray-config-ui-editor

Made for: Claude Code, Codex, Gemini CLI.

Per session 40 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 664 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

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.

Model	Per session	Once invoked
Fable 5	$0.00040	$0.00664
Opus 5	$0.00020	$0.00332
Sonnet 5	$0.00008	$0.00133
Haiku 4.5	$0.00004	$0.00066

Measured yesterday against content hash 9bbb2f813246, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

xray-ui-dev 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 yesterday.

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.

.gemini/skills/xray-ui-dev/SKILL.md · 58 lines

How it starts

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

Xray UI Dev

This skill provides specialized knowledge for developing the Xray Config UI Editor, a static web-based GUI for Xray-core.

Tech Stack & Workflow

Runtime: Bun (use bun install, bun run dev, bun run build)
Frontend: React 19 (TypeScript), Vite 7
Styling: Tailwind CSS 4
State Management: Zustand 5 + Immer (see src/store/configStore.ts)
Icons: Phosphor Icons (@phosphor-icons/react)
Visuals: React Flow (@xyflow/react) for topology visualization
Editor: Monaco Editor (@monaco-editor/react) for JSON editing

State Management (Zustand)

The application state is managed in src/store/configStore.ts.

Use useConfigStore to access the Xray configuration and Remnawave state.
Actions use immer for immutable updates.
Configuration is persisted in localStorage under xray-config-storage.

Common Actions

updateSection(section, data): Replaces a top-level Xray config section.
addItem(section, item): Adds an inbound or outbound.
updateItem(section, index, item): Updates a specific item in a list.
saveToRemnawave(): Pushes the current config to the linked Remnawave profile.

Xray Configuration Logic

Schema: Valid Xray-core configuration is defined in src/utils/config.schema.json.
Validation: Critical validation (e.g., for balancers) is performed before saving to Remnawave (see src/utils/validator.ts).
Protocols: Supports VMess, VLESS, Trojan, Shadowsocks, Hysteria2, Wireguard, etc.

UI Components

Modals: Most editing happens in modals located in src/components/editors/.
UI Elements: Reusable components are in src/components/ui/ (Button, Icon, Modal, etc.).
Topology: Traffic flow visualization is in src/components/topology/.

Key Files to Reference

src/store/configStore.ts: Central state and logic.
src/utils/config.schema.json: Complete Xray-core config specification.
src/utils/remnawave-client.ts: API client for Remnawave integration.
src/utils/validator.ts: Configuration validation logic.

Read the full file on GitHub · 58 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.

yesterday First seen · 58 lines · 40 tokens per session scan A 9bbb2f813246

Subscribe to this mod's changes

xray-ui-dev is a skill published in the GitHub repository bropines/xray-config-ui-editor (107 stars, last pushed 7d ago), licensed MIT. It adds 40 tokens to every session and 664 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.

Frontend

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

babysit-pr

Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…

openai/codex · 114 tokens

imagegen

Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…

openai/codex · 113 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens