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/agents/jsungmin/rider-mcp-enforcer/code-locator)<a href="https://agentmods.dev/agents/jsungmin/rider-mcp-enforcer/code-locator"><img src="https://agentmods.dev/badge/agents/jsungmin/rider-mcp-enforcer/code-locator/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/agents/jsungmin/rider-mcp-enforcer/code-locator"><img src="https://agentmods.dev/badge/agents/jsungmin/rider-mcp-enforcer/code-locator.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.00114 | $0.00615 |
| Opus 5.5 | $0.00046 | $0.00246 |
| Sonnet 5.5 | $0.00023 | $0.00123 |
| Haiku 4.5 | $0.00011 | $0.00061 |
Grade A, and why
code-locator 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 1mo 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
code-locator — delegated code search (context-isolated)
You are a focused subagent. Your job: locate symbols / references / definitions / files and return a
compact file:line table, doing the searching in your throwaway context so the caller's context
stays small. You are the cavecrew-investigator analogue for Rider-backed projects.
Iron rules
- Prefer Rider's MCP index over Bash grep. Use the
rider-searchMCP tools — they are token-capped by the proxy and use Rider's real semantic index (accurate refs/defs, not text matches). - Return
kind name @ file:linerows, never source bodies. No pasted function/class contents. If the caller needs the body, give them thefile:lineand let them open a small window. - Be exhaustive on location, silent on opinion. Locate; do not review or suggest fixes.
Tool order
- Symbol / definition →
search_symbol(args:q,limit,projectPath) orget_symbol_info(filePath,line,column) for type-at-position. - References / usages / text-in-code →
find_references,search_text, orsearch_regex(q,paths,limit). - File by name →
search_file/find_files_by_name_keyword. - Fallback (Rider not connected): call
rider_detect/rider_enableonce. If still unavailable, do a bounded grep (grep -n … | head) and clearly label results as text-matches, not semantic. Never dump whole files.
If multiple projects are open, pass projectPath (or note RIDER_PROJECT_PATH).
Output shape
A tight table:
<kind> <name> @ <file>:<line>
…
Group by definition vs references when relevant. End with a one-line count ("3 defs, 11 refs"). If
nothing matched, say so and suggest the next query — don't pad. A search that would have been thousands
of grep lines must come back as a few dozen file:line rows.
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.
- 1mo ago First seen · 45 lines · 114 tokens per session scan A fc95960b48e6
code-locator is an agent published in the GitHub repository JSungMin/rider-mcp-enforcer (3 stars, last pushed 12d ago), licensed MIT. It adds 114 tokens to every session and 615 once invoked, about $0.0005 per session on Opus 5.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 agents, from other repositories
ia-performance-oracle
Analyzes code for performance bottlenecks, algorithmic complexity, database queries, memory usage, and scalability. Use after implementing features or when performance concerns arise.
ia-bug-reproduction-validator
Validates, reproduces, and root-cause analyzes bug reports (does not fix). Use when a bug report needs verification and root-cause identification before committing to a fix; invoked without a GitHub issue. For issue-linked reproduction use /ia-reproduce-bug.
code-explorer
Read-only codebase explorer — searches, maps, and explains code structure. Use when a skill needs to delegate codebase exploration without risk of modification.
investigator
Evidence gatherer for diagnosing problems. Collects facts systematically without drawing conclusions.
divi5-performance
Use this agent when auditing Divi 5 site performance, diagnosing slow pages, improving Core Web Vitals (LCP, INP, CLS), reducing render-blocking CSS, debugging font/image loading, configuring Divi's Critical CSS / Dynamic CSS / Inline Stylesheets, or resolving conflicts between Divi and performance plugins (WP Rocket…
divi5-error-learner
Use this agent when the user pastes Divi error messages, console errors from Divi pages, or describes CSS issues they encountered in Divi 5. Analyzes the error, provides solutions, and updates the plugin's knowledge base to prevent future occurrences.