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 sonereraslan/local-marketplace --skill using-superunitygit clone --depth 1 https://github.com/sonereraslan/local-marketplaceWrote 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/sonereraslan/local-marketplace/using-superunity)<a href="https://agentmods.dev/skills/sonereraslan/local-marketplace/using-superunity"><img src="https://agentmods.dev/badge/skills/sonereraslan/local-marketplace/using-superunity.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.00095 | $0.01157 |
| Opus 5 | $0.00048 | $0.00579 |
| Sonnet 5 | $0.00019 | $0.00231 |
| Haiku 4.5 | $0.00010 | $0.00116 |
Grade A, and why
using-superunity 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 — 96 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Priority
Skill invocation is the highest priority action. Always invoke applicable skills before any other response, including clarifying questions. If there is even a small chance a skill applies, invoke it first — if it turns out to be wrong for the situation, you can disregard it.
How to Access Skills
Use the Skill tool. When you invoke a skill, its content is loaded and presented to you — follow it directly. Never use the Read tool on skill files.
Using SuperUnity Skills
The Rule
Invoke relevant or requested skills BEFORE any response or action. Even a small chance a skill might apply means invoke it. If the skill turns out to be wrong for the situation, you don't need to use it.
Skill Invocation Flow
- Receive user message
- Check if it's Unity-related
- If yes, check if any skill applies
- Invoke the skill using the Skill tool
- Announce: "Using [skill] to [purpose]"
- If the skill has a checklist, create a task per item
- Follow the skill content exactly
- Respond (including any clarifications)
If the task is not Unity-related, respond normally.
Available Skills
| Skill | When to Use |
|---|---|
superunity:unity-exploring-project |
Before any creative/feature work — explore project context, intent, design before code |
superunity:unity-writing-plans |
Have spec/requirements, need implementation plan before coding |
superunity:unity-executing-plans |
Have a written plan, need to execute it with review checkpoints |
superunity:unity-subagent-dev |
Executing plan with independent tasks, dispatch subagent per task |
superunity:unity-systematic-debugging |
Any bug, test failure, or unexpected behavior |
superunity:unity-tdd |
Implementing any feature or bugfix — write test first |
superunity:unity-code-review |
After completing tasks or before merging |
superunity:unity-verification |
About to claim work is complete — evidence before claims |
superunity:unity-finishing-branch |
Implementation complete, need to integrate the work |
superunity:unity-ecs-patterns |
Working with Unity DOTS — ECS, Job System, Burst Compiler, baking, authoring components |
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 · 96 lines · 95 tokens per session scan A d9266f76419c
using-superunity is a skill published in the GitHub repository sonereraslan/local-marketplace (2 stars, last pushed 4mo ago), licensed MIT. It adds 95 tokens to every session and 1,157 once invoked, about $0.0005 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
reflection-method-call
Call a C# method by reflection — including private methods. Requires a method schema obtained via 'reflection-method-find'. Supports static methods, instance methods (with optional target deserialization), and main-thread / off-thread execution.
script-execute
Compiles and executes C# code dynamically using Roslyn. Supports a full-code mode (default) and a body-only mode — see the skill body for the difference and for how to pass Unity object references as parameters.
reflection-method-find
Find C# methods across every loaded assembly by name / type / parameters — including private methods. Returns serialized MethodData entries usable as schemas for 'reflection-method-call'.
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).
script-update-or-create
Write a .cs script file (create or overwrite) with the provided C# code. Validates syntax via Roslyn before write — invalid code is rejected with error details and the file is left untouched. Refreshes the AssetDatabase and delivers the final result via requestId after Unity finishes the triggered compilation. Use…
script-delete
Delete one or more .cs script files from disk, refresh the AssetDatabase, and wait for Unity compilation to settle before delivering the final result via the request's requestId. Pair with 'script-read' to inspect files before deletion.