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 metaspartan/cybara --skill game-uigit clone --depth 1 https://github.com/metaspartan/cybaraWrote 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/metaspartan/cybara/game-ui)<a href="https://agentmods.dev/skills/metaspartan/cybara/game-ui"><img src="https://agentmods.dev/badge/skills/metaspartan/cybara/game-ui.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector pass
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.00038 | $0.00406 |
| Opus 5 | $0.00019 | $0.00203 |
| Sonnet 5 | $0.00008 | $0.00081 |
| Haiku 4.5 | $0.00004 | $0.00041 |
Grade A, and why
game-ui 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 4d 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 — 39 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Game UI
Establish the interaction model
Identify the genre, camera, primary player verbs, input devices, target platforms, safe areas, localization scope, accessibility requirements, and which information must remain visible during play.
Design rules
- Protect the center of the playfield and aiming, movement, or puzzle-critical regions.
- Give critical state clear hierarchy; move secondary detail into contextual or dismissible surfaces.
- Keep visual language consistent with the game rather than defaulting to application dashboards.
- Make focus ownership explicit when menus, dialogs, inventories, chat, or text input open.
- Pause or gate gameplay and camera input when an overlay requires exclusive interaction.
- Support keyboard, pointer, controller, and touch navigation that matches the target platform.
- Preserve safe areas, readable text scaling, localization expansion, contrast, and reduced motion.
- Avoid per-frame UI rebuilding when event-driven updates are sufficient.
Implementation
Use the chosen engine's established UI system and project patterns. Keep UI state separate from simulation truth, derive presentation from stable game state, and keep screen transitions reversible. Make loading, empty, disabled, error, disconnected, and save-in-progress states visible.
Verification
- Exercise the HUD during active gameplay rather than only in an isolated preview.
- Navigate every changed surface with each supported input family.
- Verify focus restoration and gameplay input suppression around overlays.
- Test narrow, wide, high-density, and safe-area-constrained layouts in scope.
- Capture screenshots with representative content, long labels, warnings, and low-resource states.
- Check frame time and allocation behavior while rapidly changing HUD state.
Completion criteria
Report the UI states exercised, input devices, resolutions or safe areas, accessibility checks, screenshots, and any platform-native behavior that remains unverified.
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.
- 4d ago First seen · 39 lines · 38 tokens per session scan A f71564096bd7
game-ui is a skill published in the GitHub repository metaspartan/cybara (28 stars, last pushed today), licensed MIT. It adds 38 tokens to every session and 406 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-09-03.
Other skills, from other repositories
uiux-ui-ux-pro-max
Skill "uiux-ui-ux-pro-max" from KornLabs/truss, covering ui/ux pro max - design intelligence, when to apply, rule categories by priority, running the search tool and workflow.
composio-canvas-design
Skill "composio-canvas-design" from KornLabs/truss, covering design philosophy creation, the critical understanding, how to generate a visual philosophy, philosophy examples and essential principles.
superpowers-brainstorming
Skill "superpowers-brainstorming" from KornLabs/truss, covering brainstorming ideas into designs, anti-pattern: "this is too simple to need a design", checklist, process flow and the process.
uiux-design
Skill "uiux-design" from KornLabs/truss, covering design, when to use, sub-skill routing, logo design (built-in) and logo: generate design brief.
uiux-ui-styling
Skill "uiux-ui-styling" from KornLabs/truss, covering ui styling skill, reference, when to use this skill, core stack and component layer: shadcn/ui.
anthropic-frontend-design
Skill "anthropic-frontend-design" from KornLabs/truss, covering frontend design, ground it in the subject, design principles, restraint and self-critique and more on writing in design.