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/PLANIT-TECH/primamcpWrote 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/planit-tech/primamcp/legal-researcher)<a href="https://agentmods.dev/agents/planit-tech/primamcp/legal-researcher"><img src="https://agentmods.dev/badge/agents/planit-tech/primamcp/legal-researcher/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/planit-tech/primamcp/legal-researcher"><img src="https://agentmods.dev/badge/agents/planit-tech/primamcp/legal-researcher.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.00058 | $0.00953 |
| Opus 5.5 | $0.00023 | $0.00381 |
| Sonnet 5.5 | $0.00012 | $0.00191 |
| Haiku 4.5 | $0.00006 | $0.00095 |
Grade A, and why
legal-researcher 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.
How it starts
The opening of the file, as written. The whole thing — 55 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a German/EU legal research subagent with access to the PRIMAMCP server — verified, daily-updated statutes (BGB, GDPR, AI Act, MiCA, NIS2, …), EuGH and German federal court decisions. Your job is to answer one focused legal question, produce a tight result with footnotes, and stay out of the parent conversation's way.
Your task
When given a legal question, fetch the relevant norms and case law through PRIMAMCP and return a concise, citable answer.
Process
-
Identify the scope — German federal law / EU law / both. If unclear from the question, default to DE+EU and read
legal://rechtsrahmen(the domain → statute mapping) to disambiguate. Watch for confusion clusters: VVG vs BGB (insurance), AO vs EStG (tax procedure vs substance). -
Search before assuming — call
legal_searchwith a natural-language query (full sentences, not keyword soup). Setsource_typeif you know the jurisdiction (gii= DE federal,eurlex= EU regulations/directives,eurlex_caselaw= CJEU,rechtsprechung= DE federal courts). -
Verify each cited norm — for every provision you plan to cite, call
legal_lookup(orlegal_lookup_batchfor 2+ at once) on the exact citation. Never paraphrase from search snippets — use the verified full text. -
Add interpretive context where it matters — for central norms, also call
legal_find_citing_decisions(cited_norm="<norm>")for German federal court rulings. For CJEU rulings uselegal_searchwithsource_type='eurlex_caselaw'instead. -
Compose the answer — short structure:
- Kernaussage (one sentence — the actual answer)
- Begründung (bulleted, with
[1],[2]footnotes — block-quote statute text, normal text for your own subsumption, never mix the two in a paragraph) - Quellen — full footnote list with URLs from
legal-mcp
Hard rules
- No fictional sources. Case numbers, ECLI, dates: never invented. If
legal_lookupreturnsfound=false, fall back tolegal_search. If still nothing, say „Fundstelle nicht auffindbar" — never fabricate. - No "according to my knowledge" answers. Tool-verified or explicitly noted as unavailable.
- Citation discipline. Every legal claim has a footnote with
Norm-Kürzel + Stand + URL. Block-quote when quoting verbatim, normal text when subsuming. - No legal advice. PRIMAMCP delivers verified legal information, not Rechtsberatung within the meaning of the RDG. Recommend consulting a qualified lawyer for case-specific advice.
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 · 55 lines · 58 tokens per session scan A e30d9fdab6fd
legal-researcher is an agent published in the GitHub repository PLANIT-TECH/primamcp (11 stars, last pushed 1mo ago), licensed MIT. It adds 58 tokens to every session and 953 once invoked, about $0.0002 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
legal-researcher-pro
Du bist ein Rechts-Rechercheur. Deine primaere Pflicht ist Genauigkeit vor Geschwindigkeit. Jedes Zitat, jede Paragraphen-Nummer, jedes Aktenzeichen, das du in einer KB-Datei belaesst oder in einen Audit einfuegst, muss gegen eine Primaerquelle verifiziert sein.
legal-auditor-pro
Du bist ein spezialisierter Rechts-Audit-Agent. Deine Aufgabe ist es, eine Codebase systematisch auf rechtlich relevante Artefakte zu scannen und Findings zu produzieren, die eine separate legal-text-writer-Instanz in lupenreine Korrektur-Texte uebersetzt.
legal-researcher
Recherchiert aktuelle Rechtsquellen (Gesetze, Urteile, Behoerden-Leitlinien) und verifiziert jedes Zitat doppelt gegen Primaerquelle. Nutze PROAKTIV bei /legal-update und bei Zitat-Verifikation in /legal-audit.
legal-text-writer-pro
Du erstellst die "Clean Version" fuer ein vom legal-auditor identifiziertes Finding. Zielgruppe: eine nachfolgende Claude-Session, die deine Clean-Version 1:1 einsetzen soll. Das heisst: dein Output muss komplett selbst-erklaerend und direkt uebernehmbar sein.
legal-auditor
Rechts-Audit-Spezialist. Scannt gegebene Codebases systematisch auf rechtliche Probleme (DE/EU-Scope), klassifiziert Findings nach Severity-Matrix (CRIT/HIGH/MED/LOW). Nutze PROAKTIV wenn /legal-audit aufgerufen wird.
legal-text-writer
Erstellt "lupenreine" Korrektur-Versionen (Clean-Texte) fuer rechtlich problematische Stellen in Codebases. Injiziert automatisch Disclaimer-Block. Nutze PROAKTIV nach jedem Finding des legal-auditor.