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 skills add NotNull92/hera-agent-godot --skill ui-theme-qagit clone --depth 1 https://github.com/NotNull92/hera-agent-godotWrote 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/notnull92/hera-agent-godot/ui-theme-qa)<a href="https://agentmods.dev/skills/notnull92/hera-agent-godot/ui-theme-qa"><img src="https://agentmods.dev/badge/skills/notnull92/hera-agent-godot/ui-theme-qa.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.1 | $0.00151 | $0.01666 |
| Opus 5 | $0.00076 | $0.00833 |
| Sonnet 5 | $0.00030 | $0.00333 |
| Haiku 4.5 | $0.00015 | $0.00167 |
Grade A, and why
ui-theme-qa 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 8d 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 — 136 lines — stays where its author put it; the contents beside it link to each section on GitHub.
UI Theme QA (Godot, reductive)
Mechanically remove statistical design defects from a live Godot editor, over
Control nodes. It does not redesign: it snaps theme tokens to a reference
corpus and never touches copy, information order, or layout structure.
Six areas, split by what they may do:
| areas | effect | |
|---|---|---|
| enforcing | spacing · type-scale · color · contrast |
set theme_override_* (undoable) |
| report-only | containers · decoration |
proposals in the report; no mutation |
The report-only pair would have to delete or re-parent nodes, which cannot be
decided mechanically — a node that looks decorative may be a divider, and
flattening a wrapper breaks the $Path/To/Node references scripts rely on. They
measure and surface; a human decides.
Why a pipeline, not one pass: one context holding every rule while fixing a large UI lets loud items crowd out quiet rules, which get silently dropped. So inspection and enforcement are split per area, and findings live in files. The orchestrator (this context) stays thin — it holds routing only; the detailed rules and findings live in the reference doc and the findings files.
Rules SSOT: references/ui-theme-areas.md. Values: references/reference-corpus.md. Read only the area section you are working; do not load all rules into one context.
0. Prep
hera status— confirm one live editor (thelive-editorskill covers setup). If multiple, passhera --instance <pid>to every mutation.hera guidance ui— respect the returned UI mode.- Ensure git is clean or on a branch; each area fix is one commit.
- Enumerate the target Controls:
hera --ids scene tree(edited scene) — this is the static surface the checks read.
1. Inspect (parallel, static, read-only)
Dispatch one inspector per area (spacing, type-scale, color, contrast,
containers, decoration). Each:
What ships with it
2 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.
- 8d ago First seen · 136 lines · 151 tokens per session scan A 0dad37831e2e
ui-theme-qa is a skill published in the GitHub repository NotNull92/hera-agent-godot (11 stars, last pushed yesterday), licensed MIT. It adds 151 tokens to every session and 1,666 once invoked, about $0.0008 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
ux-design
Guided, section-by-section UX spec authoring for a screen, flow, or HUD. Reads game concept, player journey, and relevant GDDs to provide context-aware design guidance. Produces ux-spec.md (per screen/flow) or hud-design.md using the studio templates.
ux-review
Validates a UX spec, HUD design, or interaction pattern library for completeness, accessibility compliance, GDD alignment, and implementation readiness. Produces APPROVED / NEEDS REVISION / MAJOR REVISION NEEDED verdict with specific gaps.
game-ui-ux
Design and build game UI/UX — HUDs, menus, and overlays — that survive every screen: anchor- based responsive layout, resolution/aspect scaling and safe areas, keyboard/gamepad focus navigation, a screen/menu state stack, and event-driven (not polled) HUD updates. Engine- neutral patterns that pair with the detected…
threejs-game-ui-designer
Design premium Three.js game UI: HUDs, menus, overlays, pause/win/lose screens, settings, icon controls, touch UI, typography, responsive layout, safe areas, text fit, and UI/world cohesion.
unity-inspector
Advise on Unity Inspector authoring UX.
biome-creation
A workflow for placing rocks, trees, plants, and other reusable scene objects into a Unity biome, a themed area of a game world. It also covers regenerating the biome and checking the result with screenshots.