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.
git clone --depth 1 https://github.com/dyCuong03/unity-agent-teamWrote 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/agents/dycuong03/unity-agent-team/bug-investigation)<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.
<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>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.00046 | $0.00653 |
| Opus 5.5 | $0.00018 | $0.00261 |
| Sonnet 5.5 | $0.00009 | $0.00131 |
| Haiku 4.5 | $0.00005 | $0.00065 |
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.
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
- Define the symptom precisely — what state is wrong, when, and under what condition
trace_execution_flowfrom symptom backward to entry point- Identify writers and readers of the mutated state
get_impact_radius— what else could be affected by a fix?- 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?)
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 · 88 lines · 46 tokens per session scan A 9d0ebb052267
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.
Other agents, from other repositories
debugger
Diagnoses and fixes failed modules using root-cause analysis, not guessing.
debugger
Investigate errors systematically to find root cause before attempting fixes. Gathers evidence, analyzes patterns, and forms testable hypotheses.
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.
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…
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.
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.