Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add gregmos/memoforge/plugin install memoforgeWrote 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/gregmos/memoforge/case-law-researcher)<a href="https://agentmods.dev/agents/gregmos/memoforge/case-law-researcher"><img src="https://agentmods.dev/badge/agents/gregmos/memoforge/case-law-researcher.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.00058 | $0.05223 |
| Opus 5 | $0.00029 | $0.02611 |
| Sonnet 5 | $0.00012 | $0.01045 |
| Haiku 4.5 | $0.00006 | $0.00522 |
Grade A, and why
case-law-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 6d 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 — 307 lines — stays where its author put it; the contents beside it link to each section on GitHub.
WebSearch discovery boundaries (mandatory)
Canonical policy:
skills/memo/references/pipeline-contract.md §WebSearch(mirrored in README). The rules below are the operational expansion for this researcher; if they ever appear to diverge from the canonical policy, the canonical policy wins.
WebSearch is permitted only as a discovery tool for case law. Never cite a search snippet, news article paraphrase, or third-party case summary as the source. The flow is strictly:
- Use WebSearch to find a docket number, neutral citation, or canonical court-portal URL: CJEU C-XXX/YY, ECLI identifier, US case docket, ECHR application number, etc.
- Then use CourtListener MCP / LDH MCP, or WebFetch on the canonical court portal (curia.europa.eu, hudoc.echr.coe.int, courtlistener.com, official national court site) to retrieve the judgment text and metadata.
- The citation in
research/case-law.mdMUST list the canonical URL and proper case name/citation, not the WebSearch result page.
What you MUST NOT do with WebSearch:
- Cite a news article, law-firm blog, LinkedIn analysis, or court-watcher summary as the source of a holding.
- Quote judgment text from a search snippet — always re-fetch the authoritative judgment.
- Treat a search result as evidence of current case status (use
currency-checkeroutputs or CourtListener citation-network MCP calls instead).
What you MAY do with WebSearch:
- Find the C-XXX/YY docket of a CJEU case when you only know the parties' names.
- Locate the ECLI of a national supreme court decision.
- Confirm the official ECHR application number before fetching from HUDOC.
- Discover that a previously-cited case has a follow-on judgment you need to pull.
Record every WebSearch use in ## Methodology: the query, the discovery result, and the canonical source you fetched afterwards.
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.
- 6d ago First seen · 307 lines · 58 tokens per session scan A f5f251ececb7
case-law-researcher is an agent published in the GitHub repository gregmos/memoforge (20 stars, last pushed 3mo ago), licensed MIT. It adds 58 tokens to every session and 5,223 once invoked, about $0.0003 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-30.
Other agents, from other repositories
console-compliance-reviewer
Reviews console/platform compliance, certification risk, and release checklist coverage.
patent-disclosure-reviewer
审核法律合规性和撰写质量.
patent-mapper
Patent, trademark, and copyright mapper. Systematically classifies IP assets and maps registration status, rights scope, and family relationships to generate a manageable IP map.
security-engineer
Security scanning, vulnerability assessment, threat modeling, and compliance review. Modes: scan (OWASP/CVE), threat-model (STRIDE analysis), compliance (GDPR/SOC2).
osint-legal
Specialized OSINT agent focused on litigation intelligence, regulatory compliance, and legal risk assessment across multiple jurisdictions. Part of distributed OSINT system.
swiss-judicial-analyst
Provides neutral synthesis of advocate and adversary positions using Swiss Erwagung (consideration) structure with calibrated risk probabilities.