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 Misaka-Mikoto-Tech/agent-skills --skill locus-unity-bridgegit clone --depth 1 https://github.com/Misaka-Mikoto-Tech/agent-skillsWrote 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/misaka-mikoto-tech/agent-skills/locus-unity-bridge)<a href="https://agentmods.dev/skills/misaka-mikoto-tech/agent-skills/locus-unity-bridge"><img src="https://agentmods.dev/badge/skills/misaka-mikoto-tech/agent-skills/locus-unity-bridge/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/misaka-mikoto-tech/agent-skills/locus-unity-bridge"><img src="https://agentmods.dev/badge/skills/misaka-mikoto-tech/agent-skills/locus-unity-bridge.svg" alt="Reviewed on agentmods" width="80" 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.00052 | $0.02887 |
| Opus 5 | $0.00026 | $0.01443 |
| Sonnet 5 | $0.00010 | $0.00577 |
| Haiku 4.5 | $0.00005 | $0.00289 |
Grade A, and why
locus-unity-bridge 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 yesterday.
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 — 253 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Locus Unity Bridge
Use the bundled PowerShell client to inspect or control a real Unity Editor.
Do not rewrite its named-pipe client. Always pass the exact Unity root to
-ProjectPath; it identifies the bridge connection.
Safety
execute can run arbitrary C# in Unity. Use it only for the project and task
the user authorized. A connected bridge requires Locus to already be installed
and enabled in the target project. Do not install or repair Locus, create its
marker, launch or close Unity, or modify a project merely to connect the bridge.
Command map
The client has six top-level commands. send is a transport command: its
-MessageType selects a curated Locus protocol message. Do not treat a
message type as a value for -Command.
Top-level -Command |
Use |
|---|---|
probe |
Check package and bridge connectivity before every Unity operation. |
send |
Send one approved protocol message listed below. |
thumbnail |
Save an asset thumbnail as a local PNG. |
render-preview |
Save a Prefab/model preview as a local PNG. |
execute |
Run an authorized C# snippet. |
recompile |
Request compilation and wait through domain reload. |
All commands except recompile use -TimeoutSeconds (default 10, range
1–600) for their final pipe response. Increase it only for an operation
that is expected to take longer. recompile instead uses its dedicated timeout
options below.
Resolve the client once:
$locusBridge = Join-Path $env:USERPROFILE '.agents\skills\locus-unity-bridge\scripts\locus-unity.ps1'
1. Probe first
& pwsh.exe -NoLogo -NoProfile -NonInteractive -File $locusBridge `
-Command probe -ProjectPath 'E:\Source\SomeUnityProject'
| Status | Next action |
|---|---|
connected |
Continue with an operation. |
package_missing |
Report the expected Packages/com.farlocus.locus; installation is outside this skill. |
package_invalid |
Report the incomplete installation path; repair is outside this skill. |
bridge_not_enabled |
Ask the user to enable/connect Locus for this project. |
editor_unreachable |
Verify that the matching project is open in Unity and Locus is active. |
What ships with it
5 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.
- yesterday Changed · +115 lines · -9 tokens per session b13dc9cce31c
- 2d ago Changed · +6 lines cbff76129437
- 7d ago Changed · +36 lines 3cf7d0e8513b
- 11d ago First seen · 96 lines · 61 tokens per session scan A 3fdae865e239
locus-unity-bridge is a skill published in the GitHub repository Misaka-Mikoto-Tech/agent-skills (261 stars, last pushed yesterday), licensed MIT. It adds 52 tokens to every session and 2,887 once invoked, about $0.0003 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
anti-cheat-systems
Analyze layered game integrity defenses and select repository resources for process-memory reports, acquired-memory forensics, callback scope, behavioral measurement and driver-policy evidence. Use for DMA versus host-mediated acquisition, input provenance, replay fidelity, collector health, detector rollout/recovery…
game-hacking-techniques
Classify game-cheating threats across client memory, code injection, rendering, input, engines, kernels, DMA and remote transports. Use for repository-backed attack-surface maps, attacker prerequisites, state exposure, legitimate comparison baselines, and observable artifacts. Select engine source, capture or…
windows-kernel-security
Analyze Windows driver trust boundaries and kernel evidence for game-security research. Use for IOCTL authorization, callbacks and IRQL, driver provenance, DSE/PatchGuard, VBS/HVCI, build-specific internals, and crash or memory forensics; select repository resources for symbol comparison, ETW metadata, driver-unit…
graphics-api-hooking
Analyze Direct3D/DXGI, OpenGL, and Vulkan rendering, presentation, composition, and capture evidence. Use to distinguish API samples, PresentMon event metrics, Tracy instrumentation, compatibility translation, frame images, and validation diagnostics; review swap chains, overlays, resource lifetime, and…
reverse-engineering-tools
Investigate supplied game binaries, protection components, drivers, dumps, and traces through reproducible binary analysis. Use for repository resource selection, PE/symbol inspection, disassembly and decompilation, control/data-flow reconstruction, build comparison, obfuscation classification, and interface evidence…
game-engine-resources
Analyze Unreal, Unity, Source, Godot, and custom engine trust boundaries and select matching repository resources. Use for engine/build identification, full source versus C# reference subsets, version-matched demos, editor versus shipped plugins, reflection and object lifecycles, Mono/IL2CPP, asset schemas, and…