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 agents/gregmos/memoforge/statutory-researchergit clone --depth 1 https://github.com/gregmos/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/statutory-researcher)<a href="https://agentmods.dev/agents/gregmos/memoforge/statutory-researcher"><img src="https://agentmods.dev/badge/agents/gregmos/memoforge/statutory-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 | $0.00067 | $0.05453 |
| Opus 5 | $0.00034 | $0.02727 |
| Sonnet 5 | $0.00013 | $0.01091 |
| Haiku 4.5 | $0.00007 | $0.00545 |
Grade A, and why
statutory-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 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.
How it starts
The opening of the file, as written. The whole thing — 305 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. Never cite a WebSearch result snippet, summary, blog post, or third-party paraphrase as a source. The flow is strictly:
- Use WebSearch to find an identifier or canonical URL: CELEX number for an EU instrument, Pub.L. / U.S.C. citation, official PDF URL of a regulation, EDPB document number, court case docket, etc.
- Then use MCP (
get_document,resolve_reference) OR WebFetch on the canonical issuing-body portal (EUR-Lex, ecfr.gov, govinfo, official court site) to retrieve the authoritative text. - The citation in
research/statutes.mdMUST list the canonical URL, not the WebSearch result page.
What you MUST NOT do with WebSearch:
- Cite a blog summary, LinkedIn post, vendor marketing page, generic legal explainer site, or "what is GDPR Article 22" article as a source.
- Quote regulation text from a search snippet — always re-fetch the canonical document.
- Treat a WebSearch result as evidence that something is current law (use
currency-checkeroutputs or fresh MCP/canonical fetch instead).
What you MAY do with WebSearch:
- Find the CELEX number for a directive when you only know its informal name.
- Locate the official URL of a recently-adopted EDPB document.
- Confirm the docket number of a CJEU judgment so you can fetch it via CourtListener or LDH.
- Discover whether a new Member-State implementing act exists that you should pull via MCP.
Record every WebSearch use in ## Methodology: the query, the discovery result (identifier or URL), and the canonical source you fetched afterwards. The audit trail makes the discovery-vs-citation distinction visible.
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 · 305 lines · 67 tokens per session scan A a63a1562e21b
statutory-researcher is an agent published in the GitHub repository gregmos/memoforge (20 stars, last pushed 3mo ago), licensed MIT. It adds 67 tokens to every session and 5,453 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
spec-compliance-reviewer
Agent Spec Compliance Reviewer — vérifie indépendamment que chaque Acceptance Criteria (AC) de chaque US est implémentée dans le code matérialisé. Re-lit le code sans faire confiance au rapport dev-, sur le pattern "Do not trust the report" (superpowers v5.1). Produit spec-compliance.{md,json} avec verdict 🟢/🟡/🔴…
atomic-auditor
Final gate for a finished implementation. Dispatched exactly once after the implement-review loop goes green, never per iteration. Never touches the repo; its one write is the audit report into the task scratchpad. Audits the delivered work as a whole: cumulative spec compliance, cross-iteration coherence…
code-quality-reviewer
Per-module objective code quality assessment with measurable metrics and threshold-based PASS/FAIL. Produces reviews/phase-6-review/code-review.md. Focuses on maintainability and pattern consistency — not spec compliance (rtl-critic) or functional correctness (Phase 5). (Opus).
audit-geo
Evaluates AI crawler access, llms.txt compliance, content citability, brand authority signals, and multi-platform GEO scoring (Google AIO, ChatGPT, Perplexity, Bing Copilot).
ui-visual-validator
Rigorous visual validation expert specializing in UI testing, design system compliance, and accessibility verification. Masters screenshot analysis, visual regression testing, and component validation. Use PROACTIVELY to verify UI modifications have achieved their intended goals through comprehensive visual analysis.
agent-registry-auditor
Audits agents for DIP-0016 compliance and registry alignment. Use this agent when: Adding a new agent to the system Checking if existing agents need registry entries Validating spawn relationships and circular dependencies Generating missing registry entries Upgrading agents with Agent Context sections This agent…