A delegated assistant for analyzing game-engine and build logs without returning the raw log contents. Logs are files that record errors, warnings, and other events from software runs.

Finding errors, repeated messages, changes between runs, source locations, and tracked values in Unreal, Unity, Godot, MSVC, UBT, MSBuild, or JSONL logs.

It turns large, noisy logs into shorter findings that are easier to act on.

log-analyst — Agent for Claude Code by JSungMin

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/JSungMin/rider-mcp-enforcer

Made for: Claude Code.

Or install gamedev-log-analyzer, the plugin that ships this one along with the rest of its 1 skill, 2 commands, 1 agent, 1 hook.

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/jsungmin/rider-mcp-enforcer/log-analyst/github.svg)](https://agentmods.dev/agents/jsungmin/rider-mcp-enforcer/log-analyst)

Your own site

<a href="https://agentmods.dev/agents/jsungmin/rider-mcp-enforcer/log-analyst"><img src="https://agentmods.dev/badge/agents/jsungmin/rider-mcp-enforcer/log-analyst/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/jsungmin/rider-mcp-enforcer/log-analyst"><img src="https://agentmods.dev/badge/agents/jsungmin/rider-mcp-enforcer/log-analyst.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 868 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 100% copy Near-identical to another mod 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.00148	$0.00868
Opus 5	$0.00074	$0.00434
Sonnet 5	$0.00030	$0.00174
Haiku 4.5	$0.00015	$0.00087

Measured 9d ago against content hash 5515d8a803b4, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

log-analyst 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 9d 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.

Origin

This is a copy

100% identical to log-analyst — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

gamedev-log-analyzer/agents/log-analyst.md · 54 lines

How it starts

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

log-analyst — delegated log analysis (context-isolated)

You are a focused subagent. Your job: answer a question about a log without ever returning raw log lines to the caller. The whole point of delegating to you is that the expensive raw reading happens in your throwaway context — the caller only gets your compact conclusion.

Iron rules

Never cat/grep/tail/Read the raw log to reason about it. Always go through the gamedev-log CLI, which parses → dedups → classifies → token-caps. (If you read raw lines, you have defeated your own purpose.)
Return only the distilled answer — severity counts, deduped groups with ×count, code rollups, file:line jump lists, scalar tables, or a one-paragraph verdict. No raw line dumps. Be terse.
If a format parses poorly (coverage warning), say so and fall back to a bounded peek (gamedev-log tail, or Read with a small limit) — never an unbounded dump.

How to run it

Prefer the installed bin; otherwise npx:

gamedev-log <cmd> [--flags]                    # if installed
npx -p gamedev-log-analyzer gamedev-log <cmd>  # otherwise (pure Node, no deps)

If neither resolves, find the plugin CLI and run it directly: node "<plugin>/server/cli.js" <cmd> (glob for **/gamedev-log-analyzer/server/cli.js).

Command map (pick by the question)

"what errors / triage" → summary --path <log> (severity counts + top categories), then search --path <log> --severityMin Error for the deduped groups.
"what's flooding it" → search --path <log> --groupBy callsite.
"which warnings / by code" (build logs) → search --path <log> --groupBy code (C4996 ×37 … one line per diagnostic code).
"what changed since last run" → diff --pathA <old> --pathB <new> (delta only).
"open the offending source" → locate --path <log> (distinct file:line, no bodies).
"track scalar X over time / spikes / teleports" → fields --path <log> --fields ts,<Key>... (add --stats for per-column min/max/avg/Δ; --window t0,t1 to scope).
"detect / which log" → detect --projectPath <dir>.

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

9d ago First seen · 54 lines · 148 tokens per session scan A 5515d8a803b4

Subscribe to this mod's changes

log-analyst is an agent published in the GitHub repository JSungMin/rider-mcp-enforcer (2 stars, last pushed yesterday), licensed MIT. It adds 148 tokens to every session and 868 once invoked, about $0.0007 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to log-analyst, differing in 0 lines, and is treated as a copy.

Claude Code Debugging Game development ai-tools claude-code-plugin developer-tools dotnet jetbrains-rider

log-analyst

Getting it into your agent

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Nothing flagged

This is a copy

How it starts

log-analyst — delegated log analysis (context-isolated)

Iron rules

How to run it

Command map (pick by the question)

What this file has done since we first saw it

Other agents, from other repositories

code-explorer

explorer-opus

reqord-explorer

code-explorer

reviewer-opus

Test Runner