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.
git clone --depth 1 https://github.com/MnkyArts/hytale-skillsnpx agentmods add skills/mnkyarts/hytale-skills/hytale-ui-windowsWrote 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/mnkyarts/hytale-skills/hytale-ui-windows)<a href="https://agentmods.dev/skills/mnkyarts/hytale-skills/hytale-ui-windows"><img src="https://agentmods.dev/badge/skills/mnkyarts/hytale-skills/hytale-ui-windows/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/mnkyarts/hytale-skills/hytale-ui-windows"><img src="https://agentmods.dev/badge/skills/mnkyarts/hytale-skills/hytale-ui-windows.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00061 | $0.10156 |
| Opus 5 | $0.00030 | $0.05078 |
| Sonnet 5 | $0.00012 | $0.02031 |
| Haiku 4.5 | $0.00006 | $0.01016 |
Grade A, and why
hytale-ui-windows 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 11d 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 — 1,561 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Hytale UI Windows
Complete guide for creating custom UI windows, container interfaces, and interactive menus in Hytale server plugins.
When to use this skill
Use this skill when:
- Creating custom inventory windows
- Building container interfaces (chests, benches)
- Implementing crafting UI systems
- Making interactive menus
- Handling window actions and clicks
- Syncing window state between server and client
- Creating .ui layout files for custom pages
- Designing HUD elements and overlays
UI System Overview
Hytale's UI system consists of two main approaches:
-
Window System (Java) - For inventory containers, crafting benches, and block-tied UIs
- Uses
Windowclasses withWindowManager - Sends JSON data via
getData() - Handles predefined
WindowActiontypes
- Uses
-
Custom UI Pages (Java) - For dynamic forms, lists, dialogs, and interactive pages
- Uses
CustomUIPageclasses withPageManager - Loads
.uifiles dynamically viaUICommandBuilder - Binds events with typed data via
UIEventBuilder
- Uses
Both systems use client-side .ui files to define visual layout and styling.
.ui Files
UI files (.ui) are client-side layout files that define the visual structure of windows and pages. They use a declarative syntax with:
- Variables (
@Name = value;) - Reusable values and styles - Imports (
$C = "path/to/file.ui";) - Reference other UI files - Elements (
WidgetType { properties }) - UI widgets with nested children - Templates (
$C.@TemplateName { overrides }) - Instantiate reusable components
IMPORTANT: File Location
All .ui files MUST be placed in resources/Common/UI/Custom/ in your plugin JAR.
your-plugin/
src/main/resources/
manifest.json # Must have "IncludesAssetPack": true
Common/
UI/
Custom/
MyPage.ui # Your custom UI files go here
MyHud.ui
ListItem.ui
Requirements:
- Your
manifest.jsonMUST contain"IncludesAssetPack": true - UI files go in
resources/Common/UI/Custom/(NOTassets/Server/Content/UI/Custom/) - In Java code, reference files by filename only:
commandBuilder.append("MyPage.ui")
What ships with it
4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 11d ago First seen · 1,561 lines · 61 tokens per session scan A f50dcdf0fa98
hytale-ui-windows is a skill published in the GitHub repository MnkyArts/hytale-skills (5 stars, last pushed 7mo ago), licensed MIT. It adds 61 tokens to every session and 10,156 once invoked, about $0.0003 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-31.
Other skills, from other repositories
worker-visualizer
A real-time data/particle/simulation visualizer whose heavy compute runs in a Web Worker (off the main thread), optionally sharing memory with the UI via SharedArrayBuffer, and renders to a canvas at 60fps. Produced as a single self-contained index.html. Use when the brief asks for a "web worker", "simulation"…
react-three-fiber
React Three Fiber 3D renderer for json-render. Use when working with @json-render/react-three-fiber, building 3D scenes from JSON specs, rendering meshes/lights/models/environments, or integrating Three.js with json-render catalogs.
vgpu
Build, debug, test, and optimize WebGPU projects using vgpu, its CLI, or @vgpu packages. Use for vgpu API questions, WGSL workflows, browser or Node rendering, integrations, testing, and performance work.
matterjs
Use when implementing 2D physics interactions with Matter.js, including Engine/World setup, Render/Runner configuration, adding bodies and constraints, and scroll/interaction-friendly canvas scenes.
html-to-ugui
A pipeline for turning HTML interface prototypes into Unity UGUI Prefabs, which are reusable Unity interface objects. It uses browser-rendered layout data to preserve positions, images, text, controls, and device-adaptation intentions.
threejs-game-director
Entrypoint for building, upgrading, and finishing Three.js browser games. Routes work across the sibling threejs- skills for gameplay, graphics, UI, 3D/image/audio asset generation, debugging, and release. Use for build-a-game, upgrade, polish, premium, AAA, high-fidelity, showcase, from-scratch, endless runner…