cursor

A project rule for Unity Editor work that requires using the hera-agent-unity command-line tool to inspect and control a running Unity project.

In plain words
What is it for?
Use it when checking the Unity connection, inspecting editor data, running C# in Unity, testing play mode, or verifying Unity changes.
Why use it?
It helps an agent verify the actual Unity editor, console, play mode, and live project state instead of relying on guesses about the project.

Cursor rule

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 rules/notnull92/hera-agent-unity/cursor
Clone the repo
git clone --depth 1 https://github.com/NotNull92/hera-agent-unity
Per session 1,131 This file is loaded in full into every session.
When invoked 1,131 The same file — it is already loaded in full.
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.01131 $0.01131
Opus 5 $0.00566 $0.00566
Sonnet 5 $0.00226 $0.00226
Haiku 4.5 $0.00113 $0.00113

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

Security

Grade A, and why

cursor 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.

examples/rules/cursor.mdc · 75 lines

How it starts

The opening of the file, as written. The whole thing — 75 lines — stays where its author put it; the contents beside it link to each section on GitHub.

hera-agent-unity — Project Rule

For any Unity Editor task in this project, always reach for the hera-agent-unity CLI first. It bridges directly to the running Editor over localhost HTTP, so you can execute C# inside Unity, read the actual console, drive Play Mode, and inspect live types — instead of guessing APIs from training data.

Bootstrap on discovery

When the user says any of "find hera-agent-unity", "hera-agent-unity 찾아봐", "is it installed?", "check the editor connection", "에디터 붙어있어?" — or anything in that family — run this sequence without asking:

  1. hera-agent-unity doctor --json
  2. hera-agent-unity status
  3. hera-agent-unity list --compact

Report one line: Connected: <project> · port=<N> · unity=<version> · state=<state> · tools=<N>. If any step fails, surface the error verbatim and stop — do not silently retry.

Ultra Hera

Ultra Hera helps AI check its Unity work. Hera does not do the AI work by itself; it tells agents how carefully to verify Unity work after using Hera.

Modes are saved in asset-config.json as loopEngineeringMode:

  • off: no extra checking rule.
  • light (default): use the Light loop for every Unity coding, Editor, and Inspector task.
  • ultra: use the Light loop for every task, then upgrade strict or important work to the Ultra loop.

Light loop: confirm the goal, observe only needed state, change code/scene/Inspector, verify compile or state, check console errors, re-read only the changed target, retry 1-2 times if needed, and report short evidence.

Ultra loop: compile, confirm console errors are 0, re-read Inspector/GameObject/asset state, run PlayMode or Unity tests, capture a screenshot if needed, and report evidence plus remaining risk.

When to use it

Need Command
What does this type look like in our Unity? hera-agent-unity describe_type UnityEditor.EditorApplication
Test an assumption hera-agent-unity exec "return EditorSceneManager.GetActiveScene().name;"
See real console errors hera-agent-unity console --type error
Drive Play Mode hera-agent-unity editor play --wait
Run tests hera-agent-unity test --mode PlayMode
Discover the full catalogue hera-agent-unity list --compact
Handoff object references cheaply hera-agent-unity find_gameobjects --ids

Read the full file on GitHub · 75 lines

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 First seen · 75 lines · 1,131 tokens per session scan A 807fbc0204a9

Subscribe to this mod's changes

cursor is a cursor rule published in the GitHub repository NotNull92/hera-agent-unity (28 stars, last pushed 13d ago), licensed Apache-2.0. It adds 1,131 tokens to every session, about $0.0057 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.