investigation

investigation is a skill for Claude Code from dyCuong03/unity-agent-team. It costs 52 tokens per session (1,037 once invoked), scanned A, original, MIT.

A read-only investigation toolkit for Unity projects that gathers information from the editor, source code, logs, compilation checks, and performance snapshots. It is intended for agents investigating systems and bugs.

In plain words
What is it for?
Use it to check compilation, inspect compile errors, read Unity editor state, analyse logs, trace code, and review performance information.
Why use it?
It gives investigations an ordered way to find existing project knowledge and diagnostic evidence before changing code, reducing guesswork when tracing errors or performance problems.

Skill for Claude Code

Written for Claude Code: installed under .claude/. Also seen: mentions Codex.

Good fit Use it to check compilation, inspect compile errors, read Unity editor state, analyse logs, trace code, and review performance information.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/dycuong03/unity-agent-team/investigation
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.

Any agent
npx skills add dyCuong03/unity-agent-team --skill investigation
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.

agentmods badge for investigation

README.md
[![agentmods](https://agentmods.dev/badge/skills/dycuong03/unity-agent-team/investigation/github.svg)](https://agentmods.dev/skills/dycuong03/unity-agent-team/investigation)
Your own site
<a href="https://agentmods.dev/skills/dycuong03/unity-agent-team/investigation"><img src="https://agentmods.dev/badge/skills/dycuong03/unity-agent-team/investigation/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.

agentmods 80×15 button for investigation

Your own site · 80×15
<a href="https://agentmods.dev/skills/dycuong03/unity-agent-team/investigation"><img src="https://agentmods.dev/badge/skills/dycuong03/unity-agent-team/investigation.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 52 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,037 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00052 $0.01037
Opus 5.5 $0.00021 $0.00415
Sonnet 5.5 $0.00010 $0.00207
Haiku 4.5 $0.00005 $0.00104

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

Security

Grade A, and why

investigation 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/skills/investigation/SKILL.md · 122 lines

How it starts

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

Unity Investigation Skills

Investigation agents use this layer for live Unity Editor evidence. CRG (code-review-graph) is always the primary tool. Unity-Skills REST provides supplementary runtime evidence.

Investigation Priority Order

  1. Check workspace/repo-knowledge.md — prior architectural knowledge
  2. Check workspace/ecs-registry.md — known component/system ownership
  3. CRG investigation (code-review-graph) — code-level tracing
  4. unity_diagnose — aggregated Unity Editor health snapshot (REST)
  5. Specific REST skills — only when 1–4 leave gaps

Never skip to REST skills without first checking workspace files and CRG.

Aggregated Diagnostic (always first REST call)

GET /skills/unity_diagnose

Returns: compilation status, play mode state, active scene, error count, memory summary. Use this before any specific investigation skill — it often reveals the issue without further calls.

Compilation Diagnostics

Module: debug

debug_check_compilation    — check if project compiles cleanly
debug_get_errors           — get compile errors with file/line
debug_force_recompile      — trigger recompile (SemiAuto — check mode first)
debug_get_defines          — list scripting define symbols
debug_get_assembly_info    — list loaded assemblies

Use debug_check_compilation before any bug investigation. If compilation fails, fix it before investigating runtime behavior — most apparent bugs are actually compile errors.

Log Analysis

Module: console

console_get_logs           — get logs with optional filter
console_start_capture      — begin capturing (before play mode)
console_stop_capture       — end capturing
console_get_stats          — error/warning/log counts

For bug investigation: start capture before reproducing, stop after, filter by error type.

Scene State Reading

Module: perception

scene_analyze              — full scene structure analysis
scene_health_check         — check for common scene problems
scene_summarize            — brief scene summary
scene_context              — scene state for AI context
project_stack_detect       — detect project tech stack
script_dependency_graph    — dependency visualization

Read the full file on GitHub · 122 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. 11d ago First seen · 122 lines · 52 tokens per session scan A 904480d13e65

Subscribe to this mod's changes

investigation is a skill published in the GitHub repository dyCuong03/unity-agent-team (7 stars, last pushed 2mo ago), licensed MIT. It adds 52 tokens to every session and 1,037 once invoked, about $0.0002 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.

Related

Other skills, from other repositories

debug-optimize-lcp

Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…

ChromeDevTools/chrome-devtools-mcp · 99 tokens

systematic-debugging

Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.

open-metadata/OpenMetadata · 37 tokens

diagnose

Trace from a reproduced symptom to the source code that causes it. Pin the specific file and approximate line, rate confidence in the cause and clarity of the fix independently, and always propose a concrete fix.

emdash-cms/emdash · 43 tokens

repro-admin

Reproduce an EmDash admin UI bug. Attach a container, start the demo dev server, drive the admin with agent-browser using the dev-bypass session, and capture the reproduction as screenshots plus a replayable transcript.

emdash-cms/emdash · 48 tokens

log-error-digest

Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…

zebbern/claude-code-guide · 71 tokens

deck-retro

Run a fully local agent-deck retrospective over the user's own transcripts, Recall index and logs. Use when a user wants to find recurring failures or take their own finding from investigation through synthetic reproduction, a user-filed issue, a test-first fix and contributor PR handoff. Also use for weekly usage…

asheshgoplani/agent-deck · 86 tokens