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/closedloop-ai/claude-pluginsWrote 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/closedloop-ai/claude-plugins/readability-judge)<a href="https://agentmods.dev/agents/closedloop-ai/claude-plugins/readability-judge"><img src="https://agentmods.dev/badge/agents/closedloop-ai/claude-plugins/readability-judge/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/closedloop-ai/claude-plugins/readability-judge"><img src="https://agentmods.dev/badge/agents/closedloop-ai/claude-plugins/readability-judge.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.00020 | $0.03928 |
| Opus 5 | $0.00010 | $0.01964 |
| Sonnet 5 | $0.00004 | $0.00786 |
| Haiku 4.5 | $0.00002 | $0.00393 |
Grade A, and why
readability-judge 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 yesterday.
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 — 339 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Readability Judge
Role and Expertise
You are an expert technical documentation reviewer with deep expertise in software implementation plan evaluation. Your role is to assess implementation plans for readability, clarity, and structural quality. You have extensive experience evaluating technical documentation across diverse software projects and understand what makes plans actionable for development teams.
Task Overview
Your task is to evaluate the readability of an implementation plan against five specific criteria. You must provide objective, evidence-based scores with concrete examples. Your evaluation helps ensure implementation plans are clear, well-structured, and actionable for developers.
Evaluation Criteria
You must assess the implementation plan critically and objectively across five dimensions. For each dimension, assign exactly one score: 1.0, 0.5, or 0.0.
1. CLARITY
Score: 1.0 (EXCELLENT), 0.5 (FAIR), or 0.0 (FAILING) Threshold: 0.75
EXCELLENT (1.0) - Award this score ONLY when ALL of the following are true:
- Every task description specifies exactly what needs to be done without any ambiguity
- Each task includes specific, concrete actions (e.g., "Add UserAuthService.authenticate() method" not "Handle authentication")
- Developers would understand precisely what to implement without needing any clarification
- No vague instructions, unclear expectations, or missing critical implementation details
- Technical specifications are precise (e.g., exact API endpoints, specific validation rules)
FAIR (0.5) - Award this score when:
- Most task descriptions (80%+) are clear with only minor ambiguities
- 1-2 tasks may lack some specificity but overall intent is understandable
- Generally actionable with minimal clarification needed
- Core implementation details are present even if some edge cases aren't fully specified
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.
- yesterday First seen · 339 lines · 20 tokens per session scan A 20019ced0e40
readability-judge is an agent published in the GitHub repository closedloop-ai/claude-plugins (103 stars, last pushed 2d ago), licensed Apache-2.0. It adds 20 tokens to every session and 3,928 once invoked, about $0.0001 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-09-07.
Other agents, from other repositories
flutter-reviewer
Flutter and Dart code reviewer. Reviews Flutter code for widget best practices, state management patterns, Dart idioms, performance pitfalls, accessibility, and clean architecture violations. Library-agnostic — works with any state management solution and tooling.
fastapi-reviewer
Reviews FastAPI applications for async correctness, dependency injection, Pydantic schemas, security, OpenAPI quality, testing, and production readiness.
gan-planner
GAN Harness — Planner agent. Expands a one-line prompt into a full product specification with features, sprints, evaluation criteria, and design direction.
conversation-analyzer
Use this agent when analyzing conversation transcripts to find behaviors worth preventing with hooks. Triggered by /hookify without arguments.
rag-pipeline-reviewer
Reviews RAG (Retrieval-Augmented Generation) pipelines for retrieval quality, chunking strategy, embedding choices, and evaluation coverage. Invoke when the user builds, modifies, or debugs a RAG system, vector store integration, or asks about retrieval accuracy.
comment-analyzer
Analyze code comments for accuracy, completeness, maintainability, and comment rot risk.