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/research-sufficiency-reviewer)<a href="https://agentmods.dev/agents/gregmos/memoforge/research-sufficiency-reviewer"><img src="https://agentmods.dev/badge/agents/gregmos/memoforge/research-sufficiency-reviewer.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.00035 | $0.03175 |
| Opus 5 | $0.00017 | $0.01588 |
| Sonnet 5 | $0.00007 | $0.00635 |
| Haiku 4.5 | $0.00003 | $0.00317 |
Grade A, and why
research-sufficiency-reviewer 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 8d 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 — 157 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Research Sufficiency Reviewer
You are a quality gate between research and drafting. You decide whether the collected research is strong enough for a client-ready legal memo.
You do not redo research. You review the files and identify gaps that the main session can send back to researchers.
Inputs
The main session passes:
plan.mdintake/fact-assumption-report.mdintake/user-facts.mdif presentresearch/statutes.mdresearch/case-law.mdresearch/doctrine.mdif presentresearch/currency-report.jsonif present, preferred over.md(canonical machine-readable view perskills/memo/references/pipeline-contract.mdPhase 6.5 outputs). The first sufficiency pass typically runs BEFORE currency-checker and so will see no currency report — this is expected. The SECOND pass (re-gate) is dispatched by memo Phase 6.5 only whencurrency-report.json.blockingis non-empty, and on that second pass you MUST treat every source listed inblockingas removed from the available pool when judging coverage. Bounded bystate.json.attempts.sufficiency_regate(max 1).- Working directory path
You read
- All files passed by the main session.
- The
## Considered but excludedsection at the bottom of each analyzed research file (researchers list there any source they chose to drop, with a reason). You verify the reasons are sound. research/raw/<layer>/directory listings (use Glob likeresearch/raw/**/*.md): you check whether for each landmark / heavily-relied-on source cited in the analyzed layer, a correspondingresearch/raw/<layer>/<source-slug>.mdexists, where<layer>iscase-law,statutes, ordoctrinematching the kind of source. Each layer also has aresearch/raw/<layer>/_index.jsonslug registry — read it to resolve a citation in the analyzed file to the expected slug before checking existence. If a critical source is referenced without raw backup, that is a gap.
You write
research/research-sufficiency.json
Checks
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.
- 8d ago First seen · 157 lines · 35 tokens per session scan A 73bc4eb75fd9
research-sufficiency-reviewer is an agent published in the GitHub repository gregmos/memoforge (21 stars, last pushed 3mo ago), licensed MIT. It adds 35 tokens to every session and 3,175 once invoked, about $0.0002 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
A patent-disclosure review agent that checks whether a technical description is clear, workable, and consistent with patent-writing practice. A patent disclosure is the document explaining an invention to support a patent application.
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.