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/takara-ai/miru-codeWrote 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/rules/takara-ai/miru-code/miru-code-search)<a href="https://agentmods.dev/rules/takara-ai/miru-code/miru-code-search"><img src="https://agentmods.dev/badge/rules/takara-ai/miru-code/miru-code-search/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/rules/takara-ai/miru-code/miru-code-search"><img src="https://agentmods.dev/badge/rules/takara-ai/miru-code/miru-code-search.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.00267 | $0.00267 |
| Opus 5.5 | $0.00107 | $0.00107 |
| Sonnet 5.5 | $0.00053 | $0.00053 |
| Haiku 4.5 | $0.00027 | $0.00027 |
Grade A, and why
miru-code-search 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 2d 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
Miru Code Search
DO NOT use Grep, Glob, SemanticSearch, or broad file reads to explore how code works when Miru MCP is available.
Search returns compact snippets (~±15 lines around the best match). When a hit has truncated: true, its header gives path:start-end Symbol and anchor_line: read exactly those lines (ranged read) instead of rereading the whole file, and call expand with file_path and anchor_line only for neighbouring chunks.
Use Miru MCP tools:
search— one call per question; pass project root asrepo- Add
includeand/orexcludeGitignore-style glob patterns when a question targets selected files (for exampleinclude: ["src/auth/**"]).searchandlocateuse the same parameters and syntax. expand— fallback: neighbouring chunks in the same file aroundanchor_linefind_related— similar code in other files
Allowed native-tool exceptions:
- exact literal lookups such as env vars or quoted strings
- reading a file Miru already identified so it can be edited
- searching outside the indexed repo
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.
- 2d ago Changed · +23 tokens per session a25f756a29b6
- 19d ago Changed · +1 lines · +48 tokens per session 885cc4767e59
- 1mo ago First seen · 21 lines · 196 tokens per session scan A d16c6188b48e
miru-code-search is a cursor rule published in the GitHub repository takara-ai/miru-code (12 stars, last pushed 2d ago), licensed MIT. It adds 267 tokens to every session, about $0.0011 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 cursor rules, from other repositories
analyze-failures
Triage Katalon True Platform/TestOps test failures and file defects. Use when you need to investigate failed test results, classify each failure as product defect vs automation defect vs environment/data issue, cluster failures by common signature, find likely root cause from execution data, and optionally create…
minimax-m3-verification
Extended M3 verification playbook: proof selection, multimodal-grounded checks, shell checks, browser checks, and recovery loops.
minimax-m3-self-evolution
MiniMax M3 self-evolution harness: iterative refinement loops, compress-before-iterate, autonomous debugging, and recursive improvement patterns.
debugging
Use this when debugging failures, broken tests, runtime errors, or unexpected behavior.
error-handling-and-validation
A code-quality guide for handling errors, invalid inputs, edge cases, preconditions, logging, and user-friendly error messages.
test-case-to-katalon-studio
Convert Katalon True Platform/TestOps manual test cases into Katalon Studio automation inside a local Studio Test Project checkout. Use when you need to author or extend a .tc test case file and its paired Groovy script under Scripts/, keep test case variable GUIDs consistent with the .ts test suite bindings that read…