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 host-surfacegit 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/host-surface)<a href="https://agentmods.dev/skills/vucinatim/air-jam/host-surface"><img src="https://agentmods.dev/badge/skills/vucinatim/air-jam/host-surface.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.00037 | $0.00515 |
| Opus 5 | $0.00018 | $0.00258 |
| Sonnet 5 | $0.00007 | $0.00103 |
| Haiku 4.5 | $0.00004 | $0.00052 |
Grade A, and why
host-surface 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 — 53 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Host Surface
Use this skill for host presentation, overlays, room chrome, and game viewport composition.
Read First
docs/airjam/generated/host-system.mddocs/airjam/generated/project-structure.mddocs/airjam/visual-system.mdif the template already ships a shared visual languagedocs/airjam/generated/controller-ui.mdonly if the host and controller should mirror a shared visual languagedocs/airjam/composition-shell-contract.mdwhen the host lobby/join shell is part of the work
Surface Rules
- the active game surface should fill an absolute
inset-0root - avoid wrappers that constrain, crop, or offset the play surface accidentally
- keep host chrome outside the gameplay coordinate space where possible
- keep overlays layered above the game surface, not embedded into gameplay components
Composition Rules
- separate room bootstrap, shell, gameplay viewport, and overlays into distinct modules
- keep host-only orchestration in
src/host/ - keep gameplay state and rendering concerns in
src/game/ - prefer reusable overlay modules over inline one-off markup
Layout Rules
- avoid overflow bugs on the main host surface
- prefer fluid sizing over fixed panel widths and heights
- keep QR, room, pause, and status UI visually secondary to the active game
- keep readable safe margins for overlays without shrinking the gameplay surface unnecessarily
Lobby Contract Rule
For host lobby work:
- the host lobby should expose room context, QR access, join URL field, copy/open actions, and a primary start action
- prefer
useHostJoinControlsplusJoinQrOverlay,JoinUrlField,JoinUrlActionButtons,JoinUrlControls, andLifecycleActionGroupunless the game needs a fully custom shell - if the shell is fully custom, preserve the same join and lifecycle behavior contract
Anti-Patterns
- gameplay rendered inside a card, panel, or centered content column
- host shell state mixed directly into gameplay components
- overlay UI positioned by guesswork inside the game scene
- host layout choices that make the game viewport smaller than necessary
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 · 53 lines · 37 tokens per session scan A 584db5584cd5
host-surface is a skill published in the GitHub repository vucinatim/air-jam (6 stars, last pushed today), licensed MIT. It adds 37 tokens to every session and 515 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-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.
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…
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.
before-after-audit
A before-and-after screenshot workflow for checking visual changes in a Unity scene. It keeps the Scene view camera fixed, compares the two images, and sends the difference for an external review.