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/JSungMin/rider-mcp-enforcerWrote 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/plugins/jsungmin/rider-mcp-enforcer/gamedev-log-analyzer)<a href="https://agentmods.dev/plugins/jsungmin/rider-mcp-enforcer/gamedev-log-analyzer"><img src="https://agentmods.dev/badge/plugins/jsungmin/rider-mcp-enforcer/gamedev-log-analyzer/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/plugins/jsungmin/rider-mcp-enforcer/gamedev-log-analyzer"><img src="https://agentmods.dev/badge/plugins/jsungmin/rider-mcp-enforcer/gamedev-log-analyzer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
gamedev-log-analyzer 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.
This is a copy
100% identical to gamedev-log-analyzer — 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.
What it actually says
{
"name": "gamedev-log-analyzer",
"description": "Token-efficient game-engine & build log analysis for Claude Code (CLI-first). Parses, deduplicates, and classifies huge Unreal/Unity/Godot/MSVC-UBT-MSBuild logs — search by severity/category, roll up by callsite, diff runs, locate file:line, and extract decisive scalar fields. No IDE required.",
"version": "0.10.7",
"author": { "name": "JSungMin", "url": "https://github.com/JSungMin" },
"homepage": "https://github.com/JSungMin/rider-mcp-enforcer",
"repository": "https://github.com/JSungMin/rider-mcp-enforcer",
"license": "MIT",
"keywords": [
"unreal",
"unreal-engine",
"unity",
"godot",
"log-analysis",
"build-log",
"mcp",
"claude-code",
"gamedev",
"token-efficiency"
]
}
What it installs
The manifest is a name and a version. 1 skill, 2 commands, 1 agent, 1 hook travel with it, and installing the plugin installs all of them — 411 tokens a session between them. Each is measured on its own page, and each can be installed alone.
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 · 22 lines scan A 3f9a08906403
gamedev-log-analyzer is a plugin published in the GitHub repository JSungMin/rider-mcp-enforcer (2 stars, last pushed yesterday), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. A static security scan graded it A with 0 findings. It is 100% identical to gamedev-log-analyzer, differing in 0 lines, and is treated as a copy.
Other plugins, from other repositories
roslyn-mcp
Roslyn-powered C# refactoring MCP server — 50 tools for code navigation, analysis, generation, and refactoring across entire .NET solutions.
open-pr
Pre-flight checks and PR creation workflow: run tests, open a PR, code review, and check CI.
research
Process any source into a structured, compounding knowledge base with refresh capability.
review
Code review for a branch, PR, or path — structured output with severity labels and cross-file analysis.
harness-share
Compile, export, import, and sync harness configurations across Claude Code, Cursor, GitHub Copilot, Codex, OpenCode, Windsurf, Gemini CLI, and Junie.
docgen
Generate or update README, API docs, architecture overview, or changelog — always confirms before writing.