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.
npx agentmods add commands/jsungmin/rider-mcp-enforcer/setupgit 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/commands/jsungmin/rider-mcp-enforcer/setup)<a href="https://agentmods.dev/commands/jsungmin/rider-mcp-enforcer/setup"><img src="https://agentmods.dev/badge/commands/jsungmin/rider-mcp-enforcer/setup.svg" alt="Measured on agentmods" 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.00042 | $0.00516 |
| Opus 5 | $0.00021 | $0.00258 |
| Sonnet 5 | $0.00008 | $0.00103 |
| Haiku 4.5 | $0.00004 | $0.00052 |
Grade A, and why
setup 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 5d 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 — setup
Configure the plugin by writing its config file (~/.rider-mcp-enforcer/config.json), which the
proxy reads at startup. Use the rider-search MCP tools — do NOT edit the user's OS environment.
Steps:
- Detect the Rider endpoint: call the
rider_detecttool. If it finds an SSE URL, propose it. If not, tell the user to enable Rider MCP (Rider → Settings | Tools | MCP Server → Enable → Copy SSE Config) and paste the URL. - Show current settings: call
rider_config. - Gather values (ask one at a time, or an
AskUserQuestionfor the common ones):riderSseUrl— Rider MCP SSE URL (required for search)projectPath— default project root (needed when multiple projects are open in Rider)exclude— comma list of path substrings to drop (default already covers build artifacts)excludeOff,maxResults,escalateLimit,maxLineChars,summarizeTools— optional tuning
- Apply: call
rider_setupwith only the keys to change, e.g.rider_setup { "riderSseUrl": "http://127.0.0.1:64342/sse", "projectPath": "<project root>" }. - Tell the user to run
/reload-plugins(or restart) — settings are read at proxy startup.
Notes:
- Precedence is environment variable > config file > default; a same-named env var still wins.
- Shell alternative:
node "${CLAUDE_PLUGIN_ROOT}/proxy/setup.mjs" --detect, thennode "${CLAUDE_PLUGIN_ROOT}/proxy/setup.mjs" riderSseUrl=... projectPath=.... - If the
rider-searchtools are absent, the plugin's MCP server isn't running — check thatcd <plugin-dir>/proxy && npm installwas done, then/reload-plugins. - 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.
- 5d ago First seen · 33 lines · 42 tokens per session scan A 0fca5fc69e01
setup is a command published in the GitHub repository JSungMin/rider-mcp-enforcer (2 stars, last pushed 4d ago), licensed MIT. It adds 42 tokens to every session and 516 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
composite-actions
Generate, review, secure, and test composite GitHub Actions following best practices — full repo scaffold, interview-driven generation, PR creation on existing repos, SHA pinning, secrets-as-inputs, job summaries, and actionlint validation.
github-actions
Design, review, secure, and debug GitHub Actions workflows — reusable workflows, OIDC federation, SHA pinning, token scoping, promotion orchestration, and CI failure diagnosis.
datadog
Set up and troubleshoot Datadog — Agent deployment on Kubernetes, APM instrumentation, Log Management, Monitors, Dashboards, SLOs, Synthetic tests, and live incident investigation using the Datadog MCP server. Covers Terraform-managed Datadog resources.
fluxcd
FluxCD entry point — routes to the right workflow based on what you need. Live cluster issue → structured 5-workflow debug trace. Repo health check → 6-phase audit (discovery, validation, API compliance, best practices, security). Helm chart review → helmchart. Starts by asking one question to confirm the right mode.
linkerd
Linkerd-specific diagnostics — mTLS verification, proxy injection issues, authorization policy debugging, traffic management, and multi-cluster connectivity problems.
terraform
Runs through the full Terraform validation pipeline — fmt, validate, tflint, security scan — and reviews a module or plan for blast radius, IAM risk, and state impact.