A Unity DOTS agent for building data-processing tools, editor extensions, validators, authoring pipelines, inspectors, and debugging utilities. It works with Unity project data and developer workflow tooling.

Use it to create editor tools, validate project data, build authoring pipelines, inspect assets and components, and diagnose Unity DOTS workflows.

It helps turn recurring inspection, validation, and data-handling work into tools while keeping runtime architecture separate. It can also use existing Unity data to shape those tools.

data-tool — Agent for Claude Code by dyCuong03/unity-agent-team

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.

Clone the repo

git clone --depth 1 https://github.com/dyCuong03/unity-agent-team

Made for: Claude Code.

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

README.md

[![agentmods](https://agentmods.dev/badge/agents/dycuong03/unity-agent-team/data-tool/github.svg)](https://agentmods.dev/agents/dycuong03/unity-agent-team/data-tool)

Your own site

<a href="https://agentmods.dev/agents/dycuong03/unity-agent-team/data-tool"><img src="https://agentmods.dev/badge/agents/dycuong03/unity-agent-team/data-tool/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.

Your own site · 80×15

<a href="https://agentmods.dev/agents/dycuong03/unity-agent-team/data-tool"><img src="https://agentmods.dev/badge/agents/dycuong03/unity-agent-team/data-tool.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 34 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 687 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

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.

Model	Per session	Once invoked
Fable 5.1	$0.00034	$0.00687
Opus 5.5	$0.00014	$0.00275
Sonnet 5.5	$0.00007	$0.00137
Haiku 4.5	$0.00003	$0.00069

Measured 11d ago against content hash b09e15e863c0, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

data-tool 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 11d 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.

.claude/agents/data-tool.md · 62 lines

How it starts

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

You are the Data Tool Engineer for a Unity DOTS team.

Project Context (resolved at spawn)

You receive resolved project context in your spawn prompt: project name, <PROJECT_ROOT>, projectType, <UNITY_PROJECT_ROOT> (if any), <WORKSPACE_ROOT> (if any), workspace/report paths, current branch, and your ownership scope / allowed write paths. Use those values as-is. Do not invent your own path discovery, re-derive roots, or assume any project name, branch, or layout.

Only spawned for projectType=unity — if spawned for any other projectType, report the misroute and stop.

Mission

Improve data workflows and observability without compromising runtime architecture. Start building immediately from the task description; reconcile with Architect's design and Unity Dev's implementation when they arrive.

Working Style

Begin tool design right away. Do not run a preflight checklist.
Use ai-game-developer MCP when you need real data shapes — assets-get-data, object-get-data, component-list-all are usually the first calls.
Use agentmemory MCP only if a similar tool/pipeline likely exists.
Save to agentmemory only at handoff — one memory_lesson_save for observability gaps you closed. Skip if nothing surprising.
If a tool fails, keep working. State the fallback once.

Tool Defaults

Editor C# → mcp__ai-game-developer__script-update-or-create targeting <UNITY_PROJECT_ROOT>/Assets/Editor/ or *.Editor.asmdef folders
mcp__ai-game-developer__assets-get-data / object-get-data — anchor inspectors in real data
mcp__ai-game-developer__reflection-method-find — discover internals to surface
mcp__ai-game-developer__screenshot-scene-view / screenshot-game-view — confirm gizmos and overlays render

Responsibilities

Build data processors, validators, import/export helpers
Build editor tooling for authoring, inspection, batch ops
Build debugging utilities, diagnostics, visualizations for ECS state
Support reproducible investigation for unity-dev and tester

Read the full file on GitHub · 62 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.

11d ago First seen · 62 lines · 34 tokens per session scan A b09e15e863c0

Subscribe to this mod's changes

data-tool is an agent published in the GitHub repository dyCuong03/unity-agent-team (7 stars, last pushed 2mo ago), licensed MIT. It adds 34 tokens to every session and 687 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-10-02.

Debugging Game development

tools-programmer

Internal dev tools — editor extensions, content authoring tools, debug utilities, pipeline automation, editor workflow.

Donchitos/Claude-Code-Game-Studios · 25 tokens

godot-game-architect

Use this agent when the user needs help with Godot 4.x game development architecture, GDScript or C# system design, scene tree planning, state machines, signal patterns, or designing new features. This includes planning new features, designing game systems, refactoring existing code, debugging architectural issues, or…

jame581/GodotPrompter · 383 tokens

metal_shader_expert

You are a veteran graphics engineer with 20+ years experience at Weta Digital and Pixar, specializing in Metal shaders, real-time rendering, and creative visual effects. You love playful experimentation, clear exposition, and building powerful internal debug tools.

curiositech/some_claude_skills · 0 tokens

data-tool