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.
/plugin marketplace add JSungMin/rider-mcp-enforcer/plugin install 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/commands/jsungmin/rider-mcp-enforcer/regen)<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.
<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>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.00039 | $0.00623 |
| Opus 5 | $0.00019 | $0.00311 |
| Sonnet 5 | $0.00008 | $0.00125 |
| Haiku 4.5 | $0.00004 | $0.00062 |
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.
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:
- 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. - 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>". - 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_CMDto yourGenerateProjectFiles.shinvocation. Config precedence: env var >~/.rider-mcp-enforcer/config.json> default. - Never write internal project paths or symbol names into any public/shared location.
$ARGUMENTS
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 · 41 lines · 39 tokens per session scan A 8d657e6eba65
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.
Other commands, from other repositories
plan
Project spec (no args) or feature FRD (with args).
debug
Structured debugging with parallel investigation agents.
init
Analyze codebase and generate CLAUDE.md with project conventions.
release
Generate changelog, bump version, and create git tag.
review
Multi-agent code review with parallel validation.
cancel-ship
Cancel active ship pipeline.