bug-investigation

bug-investigation is an agent for Claude Code from dyCuong03/unity-agent-team. It costs 46 tokens per session (653 once invoked), scanned A, original, MIT.

A bug-tracing agent that follows a code-relationship graph before opening files. It checks past investigations, traces symptoms to their source, and examines conflicting systems and unexpected state changes.

In plain words
What is it for?
Use it to investigate bugs, trace execution paths, find competing writes, and check whether a proposed fix addresses the real cause.
Why use it?
It helps avoid guessing from isolated files and makes the suspected cause easier to verify before changing code.

Agent for Claude Code

Written for Claude Code: installed under .claude/. Also seen: model in frontmatter.

Good fit Use it to investigate bugs, trace execution paths, find competing writes, and check whether a proposed fix addresses the real cause.

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

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 bug-investigation

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

Your own site · 80×15
<a href="https://agentmods.dev/agents/dycuong03/unity-agent-team/bug-investigation"><img src="https://agentmods.dev/badge/agents/dycuong03/unity-agent-team/bug-investigation.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 46 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 653 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.00046 $0.00653
Opus 5.5 $0.00018 $0.00261
Sonnet 5.5 $0.00009 $0.00131
Haiku 4.5 $0.00005 $0.00065

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

Security

Grade A, and why

bug-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/agents/bug-investigation.md · 88 lines

How it starts

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

You are the Bug Investigation Agent.

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.

Mission

Find root cause efficiently. Trace symptom to source using CRG evidence before touching any files.

Responsibilities

  • Trace symptom origin through the execution chain
  • Identify competing systems and write conflicts
  • Detect unintended state mutations
  • Validate assumptions before proposing a fix

Step 0 — Memory Recall First

Before any CRG query, check agentmemory for prior investigations of this symptom or component:

mcp__agentmemory__memory_smart_search("<symptom keywords> <affected system name>")

If a prior investigation exists: use it as a hypothesis to verify, not a conclusion to accept. State: "Prior investigation found: . Verifying now."

If nothing found: proceed to CRG.

CRG-First Workflow

  1. Define the symptom precisely — what state is wrong, when, and under what condition
  2. trace_execution_flow from symptom backward to entry point
  3. Identify writers and readers of the mutated state
  4. get_impact_radius — what else could be affected by a fix?
  5. Inspect only the systems identified by graph evidence

Bug Investigation Chain

Symptom
→ entry point
→ mutation path
→ competing systems
→ side effects
→ root cause

Questions to Always Ask

  • Who writes this state?
  • Who mutates this component?
  • What system runs after this one?
  • What changed unexpectedly?

ECS Priority

For ECS bugs, prioritize:

  • Component writers (who adds/sets this component?)
  • System execution order (what runs before and after?)
  • Transform mutations (which system moves/scales this entity?)
  • Race or override patterns (do two systems write the same component?)

Read the full file on GitHub · 88 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 · 88 lines · 46 tokens per session scan A 9d0ebb052267

Subscribe to this mod's changes

bug-investigation is an agent published in the GitHub repository dyCuong03/unity-agent-team (7 stars, last pushed 2mo ago), licensed MIT. It adds 46 tokens to every session and 653 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 agents, from other repositories

debugger

Diagnoses and fixes failed modules using root-cause analysis, not guessing.

TT-Wang/forge · 17 tokens

debugger

Investigate errors systematically to find root cause before attempting fixes. Gathers evidence, analyzes patterns, and forms testable hypotheses.

bostonaholic/rpikit · 28 tokens

loom-advisor

Read-only advisory agent for debugging and repeated failures. Spawned instead of a blind retry when an implementer has failed twice on the same task, or a bug resists straightforward diagnosis. Returns a root-cause diagnosis plus one concrete next step.

cosmix/loom · 53 tokens

type-reconstructor

Dedicated struct/class reconstruction from IDA Pro decompiled binaries. Scans every function for memory access patterns, merges evidence across the module, resolves vtable and COM interface layouts, and generates compilable C++ header files with per-field confidence annotations. Use for full-module or single-class…

marcosd4h/DeepExtractRuntime · 63 tokens

runtime-observer

Dynamic observation agent designed to inspect running applications, trace state transitions, log API traffic, and flag race conditions, cache states, or timing issues. Trigger with "start runtime observer", "observe live system", "trace API calls", or during characterization test validation.

richfrem/agent-plugins-skills · 56 tokens

evolve-retrospective

Failure post-mortem agent for the Evolve Loop. Fires only on Auditor FAIL or WARN verdicts. Reads cycle artifacts and produces a structured retrospective + failure-lesson YAML files. READ-ONLY outside the lessons directory.

mickeyyaya/evolve-loop · 51 tokens