Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/batihandev/unity-mcp-skillsnpx agentmods add skills/batihandev/unity-mcp-skills/cameraWrote 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/batihandev/unity-mcp-skills/camera)<a href="https://agentmods.dev/skills/batihandev/unity-mcp-skills/camera"><img src="https://agentmods.dev/badge/skills/batihandev/unity-mcp-skills/camera/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/batihandev/unity-mcp-skills/camera"><img src="https://agentmods.dev/badge/skills/batihandev/unity-mcp-skills/camera.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.00019 | $0.01633 |
| Opus 5.5 | $0.00008 | $0.00653 |
| Sonnet 5.5 | $0.00004 | $0.00327 |
| Haiku 4.5 | $0.00002 | $0.00163 |
Grade A, and why
unity-camera 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 — 145 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Camera Skills
Recipe path rule:
../../recipes/camera/<command>.mdScreenshots:
Unity_Camera_Capture(native MCP) renders a camera in-memory by instance ID for quick inspection.camera_screenshot(this module) writes a PNG to a path underAssets/with custom resolution and looks the camera up by name / path / instanceId.
Overview
Control the Scene View camera.
Common Mistakes
DO NOT (common hallucinations):
camera_move/camera_rotatedo not exist → usecamera_set_transform(Scene View) orgameobject_set_transform(Game Camera)camera_set_fovdoes not exist → usecamera_set_propertieswithfieldOfViewparametercamera_*skills control two different cameras:camera_set_transform/camera_look_at/camera_align_view_to_objectcontrol the Scene View camera;camera_create/camera_set_properties/camera_screenshotcontrol Game Camerascamera_deletedoes not exist → usegameobject_deleteon the camera GameObject
Routing:
- For Cinemachine virtual cameras → use
cinemachinemodule - For Game Camera component properties →
camera_set_properties/camera_get_properties(this module) - For scene screenshots →
scene_screenshot(scene module) uses the Scene View; for in-memory Game Camera inspection useUnity_Camera_Capture; for persisted Game Camera PNGs at custom resolution usecamera_screenshot(this module)
Skills
camera_align_view_to_object
Align Scene View camera to look at an object. Parameters:
name(string, optional): Target GameObject name.instanceId(int, optional): Target GameObject instance ID.path(string, optional): Target GameObject hierarchy path.
camera_get_info
Get Scene View camera position and rotation. Parameters: None.
camera_set_transform
Set Scene View camera position/rotation manually. Parameters:
posX,posY,posZ(float): Position.rotX,rotY,rotZ(float): Rotation (Euler).size(float, optional): Orthographic size or distance.instant(bool, optional): Move instantly (default true).
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 · 145 lines · 19 tokens per session scan A e88c8089cd9e
unity-camera is a skill published in the GitHub repository batihandev/unity-mcp-skills (6 stars, last pushed 12d ago), licensed MIT. It adds 19 tokens to every session and 1,633 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
migrate-mstest-v3-to-v4
Use this skill before answering, planning, or editing any MSTest 3.x-to-4.x upgrade or post-upgrade failure. Triggers include "MSTest v4 breaking changes"; CS0507/CS0103/CS1061/CS1615; ExecuteAsync, CallerInfo, DisplayName, or custom TestMethodAttribute; ClassCleanupBehavior; ContainsKey; ThrowsExactly or…
migrate-xunit-to-mstest
Convert .NET tests from xUnit.net v2/v3 to MSTest v4 while preserving VSTest or MTP. Use for replacing xunit packages, Fact/Theory/InlineData/MemberData, assertions, IClassFixture/ICollectionFixture, ITestOutputHelper, TestContext cancellation, traits/Owner, skips, timeouts, and xUnit parallelization. Also use when a…
migrate-xunit-to-xunit-v3
Migrate .NET test projects from xUnit.net v2 to xunit.v3 and fix v3 breaks. Use for package/CPM conversion, OutputType=Exe, preserving the VSTest or MTP runner (including projects currently using YTest.MTP.XUnit2), incompatible TFMs, async void tests, string-to-Type attributes, custom Fact/Theory/BeforeAfterTest…
semantic-kernel
Build AI-enabled .NET applications with Semantic Kernel using services, plugins, prompts, and function-calling patterns that remain testable and maintainable. USE FOR: adding AI-driven prompts, plugins, or orchestration to a .NET app; reviewing kernel construction, service registration, or plugin usage; building…
wpf
Build and modernize WPF applications on .NET with correct XAML, data binding, commands, threading, styling, and Windows desktop migration decisions. USE FOR: working on WPF UI, MVVM, binding, commands, or desktop modernization; migrating WPF from .NET Framework to .NET; integrating newer Windows capabilities into a…
worker-services
Build long-running .NET background services with BackgroundService, Generic Host, graceful shutdown, configuration, logging, and deployment patterns suited to workers and daemons. USE FOR: background services; scheduled workers; hosted services; worker extraction; graceful shutdown, health checks, and service hosting…