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 AlexWortega/junoclaude --skill junogit clone --depth 1 https://github.com/AlexWortega/junoclaudeWrote 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/alexwortega/junoclaude/juno)<a href="https://agentmods.dev/skills/alexwortega/junoclaude/juno"><img src="https://agentmods.dev/badge/skills/alexwortega/junoclaude/juno.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.00121 | $0.01614 |
| Opus 5 | $0.00060 | $0.00807 |
| Sonnet 5 | $0.00024 | $0.00323 |
| Haiku 4.5 | $0.00012 | $0.00161 |
Grade A, and why
juno 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 — 141 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Juno: New Origins
The tools work directly on the game's files. All of its formats are plain XML with no signatures or checksums, so craft and flight programs can be generated programmatically.
Workflow
game_state— confirm the game is not running: you cannot write while it is.craft_read/part_lookup— understand what you are working with.vizzy_write— the flight program (start withdry_run: true).game_launch→ check in game →log_read— feedback.junoclaude_restore— roll back if something went wrong.
Every write takes a snapshot first; junoclaude_restore with no arguments lists them.
Four rules
They prevent almost every failure.
- Do not write craft XML by hand. The connection structure is not obvious (see below); use the tools.
- Do not request
craft_readinxmlmode withoutpart_ids. Craft reach 2 MB — the context will run out on the first call. Start with the summary. - Do not edit live what the game writes itself —
GameStates/,Settings.xml,Career/. Craft and flight programs can be written while the game is running: the craft list is verified not to be cached, and a new file shows up in the designer immediately. - Do not invent Vizzy property names. The compiler checks them against the catalog and suggests near matches, but it is better to check beforehand.
Coordinate system and geometry
+Yis up along the stack. A part'spositionis its center, in meters, in craft-local coordinates.rotationis Euler angles in degrees.- Bounds and mass (
price,initialBounds*,localCenterOfMass,<Drag>) are derived: the game recomputes them on load. Approximate values are enough. - Most fuselage parts are procedural:
Fuselage1is a fuel tank, an adapter and a nose cone all at once, the difference being only the<Fuselage>modifier (topScale,bottomScale, withoffset.ysetting the length). LikewiseRocketEngine1covers every rocket engine vianozzleTypeId.
What ships with it
3 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 · 141 lines · 121 tokens per session scan A 03a2af4d48e3
juno is a skill published in the GitHub repository AlexWortega/junoclaude (8 stars, last pushed 1mo ago), licensed MIT. It adds 121 tokens to every session and 1,614 once invoked, about $0.0006 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
gameobject-component-destroy
Destroy one or more Components from a target GameObject. Missing (null) components are skipped — they cannot be destroyed. Use 'gameobject-find' and 'gameobject-component-get' to identify the components first.
unity-version-split
Split a C# file into Unity 6.5+ and pre-Unity 6.5 variants. Use when a file needs different implementations for different Unity versions due to API changes (e.g., EntityId vs int, GetEntityId vs GetInstanceID).
unity-addressables
Manage Addressables groups, entries, profiles and content builds (com.unity.addressables, reflection-based).
playtest-report
Generates a structured playtest report template or analyzes existing playtest notes into a structured format. Use this to standardize playtest feedback collection and analysis.
motion
How an agent turns a character mesh into a usable animated FBX — and how to judge whether the result is shippable.
unity-manual-component
Manually add, configure, reorder, and copy components on GameObjects using Unity Editor UI. For one-off Inspector workflows that do not need REST automation.