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 vucinatim/air-jam --skill controller-uigit clone --depth 1 https://github.com/vucinatim/air-jamWrote 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/vucinatim/air-jam/controller-ui)<a href="https://agentmods.dev/skills/vucinatim/air-jam/controller-ui"><img src="https://agentmods.dev/badge/skills/vucinatim/air-jam/controller-ui/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/vucinatim/air-jam/controller-ui"><img src="https://agentmods.dev/badge/skills/vucinatim/air-jam/controller-ui.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.00034 | $0.00528 |
| Opus 5.5 | $0.00014 | $0.00211 |
| Sonnet 5.5 | $0.00007 | $0.00106 |
| Haiku 4.5 | $0.00003 | $0.00053 |
Grade A, and why
controller-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 1mo 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 — 70 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Controller UI
Use this skill for controller gameplay and lobby surfaces.
Read First
docs/airjam/generated/controller-ui.mddocs/airjam/visual-system.mddocs/airjam/iconography.mddocs/airjam/composition-shell-contract.mdwhen the controller needs lobby/status/lifecycle shell work
Gameplay Rules
- gameplay controller UI should live inside an absolute
inset-0root - avoid scroll during active gameplay
- use large touch targets
- disable accidental text selection
- keep actions obvious and single-purpose
Lobby Rules
- keep the flow simple
- allow scroll only when it helps
- keep the hierarchy sparse
- prefer the shared shell contract for top status and lifecycle action placement unless the game has a strong reason to go fully custom
Shell Contract Rule
For controller shell work:
- prefer
RuntimeShellHeader,LifecycleActionGroup,useControllerShellStatus,useControllerLifecyclePermissions, anduseControllerLifecycleIntentsfor the default composition path - if you need custom markup, keep the same lifecycle behavior and action ordering
- do not keep duplicate lifecycle controls in both a top shell and a legacy local panel
Design Direction
- build controller UI like a game control surface
- avoid card-heavy dashboards
- avoid tiny controls and dense text
- avoid emoji-as-icon UI
- if the template already defines semantic panel, shell, or touch-surface utilities, use those before inventing new visual patterns
Icon Rule
Prefer:
@tabler/icons-reactfor general UI and system actionsreact-iconsGi*exports for gameplay-specific concepts such as abilities, status effects, pickups, and damage types
Do not mix icon packs casually throughout the tree.
Prefer local wrapper modules so icon usage stays curated and replaceable.
Attribution Note
If the project uses react-icons Gi* icons, remember that the underlying Game Icons set has its own attribution requirements.
Downstream teams remain responsible for how they satisfy those requirements.
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.
- 1mo ago First seen · 70 lines · 34 tokens per session scan A c40db533e4dc
controller-ui is a skill published in the GitHub repository vucinatim/air-jam (8 stars, last pushed yesterday), licensed MIT. It adds 34 tokens to every session and 528 once invoked, about $0.0001 per session on Opus 5.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
magic-ui
Use this skill when users want to add, customize, or troubleshoot Magic UI components in React/Next.js projects. It covers component selection, shadcn registry installation (@magicui/), integration patterns, and practical quality checks for accessibility and maintainability.
roblox-ui
Build production Roblox interfaces with ScreenGui/PlayerGui lifecycle, responsive UDim2 layouts, safe insets, reusable editable Instances, cross-device input and selection, restrained motion, cleanup, and multi-viewport verification. Use for Roblox HUDs, inventories, shops, settings, ability bars, ScrollingFrames…
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…
building-canvases
Create or edit a PostHog freeform canvas — a sandboxed browser application (data board, document, form, small tool, graphics experiment) stored in PostHog and rendered by the desktop/web app. Use when a task asks to build, generate, update, or fix a standalone canvas app, or when a freeform canvas id is given as the…
composing-grid-canvases
Compose PostHog grid canvases — widget grids (including the user's home canvas) built from reusable component canvases. Use when a task asks to add, fill, move, resize, or remove a widget on a grid or home canvas, to compose a whole canvas of widgets from one ask, to build a reusable widget/component, or when a…
quill-code
Edit the @posthog/quill design system locally and consume the change in products/desktop before it is published to npm. Use when changing quill components/primitives/tokens, when a quill change must be tested inside the Code app, or when the user mentions quill, the design system, the .local-quill tarball, or the…