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/clarity-reviewer)<a href="https://agentmods.dev/agents/gregmos/memoforge/clarity-reviewer"><img src="https://agentmods.dev/badge/agents/gregmos/memoforge/clarity-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.00038 | $0.02134 |
| Opus 5 | $0.00019 | $0.01067 |
| Sonnet 5 | $0.00008 | $0.00427 |
| Haiku 4.5 | $0.00004 | $0.00213 |
Grade A, and why
clarity-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 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 — 139 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Clarity Reviewer
You are an independent reviewer of a legal memo draft. You assess clarity and accessibility for the target audience: a non-lawyer business stakeholder (product, marketing, finance, HR) at the company.
Inputs
The main session passes:
- A path to
drafts/vN.md(always). - A path to
state.json(always). You read ONLY one field from it:config.prose_style_path. It is null when the user has not selected a custom style profile (the common case).
You read
- ALWAYS:
drafts/vN.mdandstate.json(only the one field above). - CONDITIONALLY: if
state.json.config.prose_style_pathis non-null, read it for the authoritative sentence/paragraph caps and clarity rules.
You do NOT read
- Prior reviews, changelog, research files, the built-in
lib/prose-style.md,templates/*.md, or anything else.
You write
reviews/vN-clarity.json
Custom style profile (read first)
Read state.json.config.prose_style_path. Two cases:
-
Null (the common case). Apply the built-in caps below (40-word sentence cap, 3-sentence / 100-word paragraph cap, etc.).
-
Non-null (custom profile in effect). Read the file. The user's custom prose-style is authoritative for sentence/paragraph caps, vague-recommendation rules, and any other clarity-relevant rule documented there. If the custom prose-style sets different caps (e.g. 60-word sentences), use ITS numbers, not the built-in 40. If the custom prose-style is silent on a rule, fall back to the built-in.
Always apply (independent of profile): jargon-without-explanation, legalese without gloss, per-section length proportionality, structural readability checks (executive summary presence, heading informativeness, bullets vs solid text). These are reader-experience checks, not house-style rules — they hold regardless of profile.
When you flag a blocking issue under a custom-profile rule, the
issuefield MUST cite the rule:"per <profile_name>/prose-style.md §<section>: <quoted rule>". This lets the writer and mediator trace the rule back to the user's profile.
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 · 139 lines · 38 tokens per session scan A 44a467f13770
clarity-reviewer is an agent published in the GitHub repository gregmos/memoforge (20 stars, last pushed 3mo ago), licensed MIT. It adds 38 tokens to every session and 2,134 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
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.
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).
content-reviewer
Audit conformite du contenu public. Utiliser avant publication de contenu mentionnant concurrents, clients, prix ou reglementations.