uloop-get-project-info

A Unity project-inspection tool that reports project settings and computer details through the uloop command-line tool. Unity is a game and interactive-app development environment.

In plain words
What is it for?
Use it to check project metadata, runtime state, device information, operating system, processor, memory, and graphics hardware.
Why use it?
It avoids manually opening project settings or searching files to find basic details such as the Unity version, target platform, or application version.

Skill for Claude CodeCodex

Install

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.

agentmods
npx agentmods add skills/hatayama/unity-cli-loop/skill
Any agent
npx skills add hatayama/unity-cli-loop --skill skill
Clone the repo
git clone --depth 1 https://github.com/hatayama/unity-cli-loop

Made for: Claude Code, Codex.

Per session 34 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 215 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00034 $0.00215
Opus 5 $0.00017 $0.00108
Sonnet 5 $0.00007 $0.00043
Haiku 4.5 $0.00003 $0.00021

Measured yesterday against content hash 11f8f8bd5591, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

uloop-get-project-info 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.

Assets/Editor/CustomCommandSamples/GetProjectInfo/Skill/SKILL.md · 42 lines

What it actually says

uloop get-project-info

Get detailed Unity project information.

Usage

uloop get-project-info

Parameters

None.

Output

Returns JSON with:

  • ProjectName: Application product name
  • CompanyName: Company name
  • Version: Application version
  • UnityVersion: Unity Editor version
  • Platform: Current platform
  • DataPath: Assets folder path
  • IsEditor: Whether running in editor
  • IsPlaying: Whether in play mode
  • DeviceType: Device type
  • OperatingSystem: OS information
  • ProcessorType: CPU type
  • SystemMemorySize: RAM size in MB
  • GraphicsDeviceName: GPU name

Notes

This is a sample custom tool demonstrating how to create Unity CLI Loop tools.

Files

What ships with it

1 file 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.

Changes

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.

  1. yesterday Changed · +1 lines 11f8f8bd5591
  2. yesterday First seen · 41 lines · 34 tokens per session scan A fa1aa2a893f1

Subscribe to this mod's changes

uloop-get-project-info is a skill published in the GitHub repository hatayama/unity-cli-loop (522 stars, last pushed yesterday), licensed MIT. It adds 34 tokens to every session and 215 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-30.

Related

Other skills, from other repositories

unity

Compile, test, and drive Unity for this repo's C# packages (unity/core, jint, quickjs, clearscript) and the two Unity projects (tests/, kitchen-sink/). Use when a change touches C# under unity/, when Unity test results are needed, when a rendering snapshot has to be checked or regenerated, or when the app has to be…

ReactUnity/core · 108 tokens

test-designing-guide

Provides test design methodology for Unity projects. Use this skill whenever designing test cases from requirements or specifications, including selecting test techniques, deriving test cases, and formatting them. Even for small features, load this skill to ensure test design rigor.

nowsprinting/unity-coding-skills · 52 tokens

fix-bug

Diagnoses and fixes bugs using a test-first workflow (reproduce, diagnose, fix). Use this skill whenever the user reports a bug, describes unexpected behavior, or asks to investigate or fix a defect. Even if the user says "something's broken", "this isn't working", "fix this bug", or "why does X happen", load this…

nowsprinting/unity-coding-skills · 86 tokens

plan-feature

Orchestrates the test-first implementation planning workflow for feature implementation and spec changes. Use this skill whenever plan mode is active and the task involves implementing or adding a new feature, or changing an existing specification. Even if the user only says "plan this" or "how should we implement…

nowsprinting/unity-coding-skills · 76 tokens

refine-tests

Reviews existing test code for conformance to the test-designing-guide and test-writing-guide, then applies the refinements. Use this skill when the user wants to review or refine existing test code so it follows the project's test design and writing conventions. Typically invoked as /refine-tests .

nowsprinting/unity-coding-skills · 64 tokens

test-writing-guide

Provides guidelines for writing test code for Unity projects. Make sure to use this skill whenever writing, creating, editing, or modifying test code files (files under Tests/). This includes implementing new tests, fixing test failures, adding test cases, or any task that results in test code changes. Even for small…

nowsprinting/unity-coding-skills · 81 tokens