regen

regen is a command for Claude Code from JSungMin/rider-mcp-enforcer. It costs 39 tokens per session (623 once invoked), scanned A, original, MIT.

A command for regenerating Unreal Engine project files so JetBrains Rider can update its view of the source code. Unreal Engine is a tool for building games and other 3D applications; Rider is a code editor for developers.

In plain words
What is it for?
Use it to preview the project and engine command, check how they were resolved, and then regenerate the files when needed.
Why use it?
It fixes stale project information that can make existing files appear missing or leave searches empty after files are added, moved, or renamed.

Command for Claude Code

Written for Claude Code: ${CLAUDE_PLUGIN_ROOT} variable. Also seen: mentions Claude Code.

Runs only inside its plugin — its command needs a path that Claude Code sets for a plugin’s own hooks and for nothing else. Install the plugin, not this.

Part of the rider-mcp-enforcer plugin — 1 skill, 5 commands, 1 agent, 1 MCP server, 1 plugin shipped together

Good fit Use it to preview the project and engine command, check how they were resolved, and then regenerate the files when needed.

Compare 6 commands from other repositories ↓
Install

Getting it into your agent

This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.

Claude Code
/plugin marketplace add JSungMin/rider-mcp-enforcer
Claude Code
/plugin install rider-mcp-enforcer

Made for: Claude Code.

Or install rider-mcp-enforcer, the plugin that ships this one along with the rest of its 1 skill, 5 commands, 1 agent, 1 MCP server, 1 plugin.

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 regen

README.md
[![agentmods](https://agentmods.dev/badge/commands/jsungmin/rider-mcp-enforcer/regen/github.svg)](https://agentmods.dev/commands/jsungmin/rider-mcp-enforcer/regen)
Your own site
<a href="https://agentmods.dev/commands/jsungmin/rider-mcp-enforcer/regen"><img src="https://agentmods.dev/badge/commands/jsungmin/rider-mcp-enforcer/regen/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 regen

Your own site · 80×15
<a href="https://agentmods.dev/commands/jsungmin/rider-mcp-enforcer/regen"><img src="https://agentmods.dev/badge/commands/jsungmin/rider-mcp-enforcer/regen.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 39 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 623 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.00039 $0.00623
Opus 5 $0.00019 $0.00311
Sonnet 5 $0.00008 $0.00125
Haiku 4.5 $0.00004 $0.00062

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

Security

Grade A, and why

regen 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.

commands/regen.md · 41 lines

What it actually says

Rider plugin — regenerate project files

Use when Rider can't find a source file that exists on disk (searches return "doesn't exist"/empty after files were added/moved/renamed) — the generated project files are stale.

Preferred (no MCP shell-approval prompt): run the CLI yourself. Because you run it, there's no "allow MCP shell access" warning:

  1. Dry run — see what it would do, runs nothing: node "${CLAUDE_PLUGIN_ROOT}/proxy/regen.mjs" It prints the resolved .uproject, the engine (and how it was resolved), and the exact command.
  2. Review that engine + command. If wrong, pin it (no code change needed): node "${CLAUDE_PLUGIN_ROOT}/proxy/setup.mjs" regenCmd="<your generate command, {uproject}/{engine} tokens>" or ... enginePath="<engine dir>".
  3. Run it: node "${CLAUDE_PLUGIN_ROOT}/proxy/regen.mjs" --confirm (add --project="<root>" if needed).

Alternative: the rider_regen_project MCP tool. Same engine, but it spawns a build, so Claude Code will ask you to approve the tool (expected — it runs a shell command). It is dry-run-first: a call without confirm only shows the plan; pass confirm:true to execute. force:true ignores a stale lock.

After a successful regen, Rider must RELOAD the solution before its symbol index updates — accept Rider's reload prompt (it detects the .vcxproj change), or do it manually: File → Reload All from Disk (or Unreal Refresh). Only then do search_symbol / rename_refactoring resolve the new files. (A regen exiting 0 means the generator ran, not that Rider re-indexed. Rider exposes no reload trigger, so this step is manual.)

To check whether the reload took: call the MCP tool with verifyPath:"<the file that was missing>" and confirm:true — after the regen it re-probes Rider and reports (visible now) or (still missing → reload + retry). Verification needs Rider connected, so it's only on the MCP tool, not the CLI.

Notes:

  • Auto-detect is Windows-only; on macOS/Linux set RIDER_REGEN_CMD to your GenerateProjectFiles.sh invocation. Config precedence: env var > ~/.rider-mcp-enforcer/config.json > default.
  • Never write internal project paths or symbol names into any public/shared location.

$ARGUMENTS

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. 9d ago First seen · 41 lines · 39 tokens per session scan A 8d657e6eba65

Subscribe to this mod's changes

regen is a command published in the GitHub repository JSungMin/rider-mcp-enforcer (2 stars, last pushed 2d ago), licensed MIT. It adds 39 tokens to every session and 623 once invoked, about $0.0002 per session on Opus 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-08-31.