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 instructions/roop-world/legalsearch/agents-mdgit clone --depth 1 https://github.com/Roop-World/LegalSearchWrote 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/instructions/roop-world/legalsearch/agents-md)<a href="https://agentmods.dev/instructions/roop-world/legalsearch/agents-md"><img src="https://agentmods.dev/badge/instructions/roop-world/legalsearch/agents-md.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 | $0.00203 | $0.00203 |
| Opus 5 | $0.00102 | $0.00102 |
| Sonnet 5 | $0.00041 | $0.00041 |
| Haiku 4.5 | $0.00020 | $0.00020 |
Grade A, and why
LegalSearch AGENTS.md 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 4d 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
Agent Instructions for This Repository
This repository is public-facing. Keep it safe, boring, and interoperable.
Do
- Document only public Roop MCP URLs and public Roop documentation.
- Keep setup instructions vendor-neutral where possible.
- Use local environment variables for authenticated access examples.
- Make anonymous/free-limit handoff explicit.
- Tell agents to cite MCP-returned public references and disclose uncertainty.
- Preserve the message that LegalSearch enables interoperability, while Roop's native platform is the integrated home for sustained legal workflows.
Do Not
- Add non-public Roop infrastructure, hostnames, paths, operational details, source-code internals, private technical names, or privileged endpoints.
- Add raw secrets, example tokens that look real, passwords, API keys, or bearer-token literals.
- Recommend bypassing rate limits, authentication, robots guidance, packet caps, or MCP boundaries.
- Claim the MCP provides legal advice.
- Claim a pricing advantage unless the pricing has been approved and publicly published.
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.
- 4d ago First seen · 21 lines · 203 tokens per session scan A acb196f8dc40
LegalSearch AGENTS.md is an instructions file published in the GitHub repository Roop-World/LegalSearch (1 stars, last pushed 3mo ago), licensed MIT. It adds 203 tokens to every session, about $0.0010 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 instructions, from other repositories
ayunis-legal-mcp CLAUDE.md
Instructions for ayunis-core/ayunis-legal-mcp, covering legal mcp - architecture and development guide, project overview, architecture, directory structure and key components.
spain-ai-kit CLAUDE.md
Instructions for aplaceforallmystuff/spain-ai-kit, a project described as: MCP servers connecting AI applications to Spanish government open data and legal infrastructure.
law-mcp CLAUDE.md
Claude Code instructions for finalchild/law-mcp, covering claude.md, build and development commands, architecture overview, core components and key integration points.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.