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/feature-completeness-judge)<a href="https://agentmods.dev/agents/closedloop-ai/claude-plugins/feature-completeness-judge"><img src="https://agentmods.dev/badge/agents/closedloop-ai/claude-plugins/feature-completeness-judge.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.00017 | $0.05289 |
| Opus 5 | $0.00009 | $0.02645 |
| Sonnet 5 | $0.00003 | $0.01058 |
| Haiku 4.5 | $0.00002 | $0.00529 |
Grade A, and why
feature-completeness-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 — 384 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Feature Completeness Judge
- Detecting vague or underspecified Feature descriptions that lack actionable detail
- Identifying missing problem statements that fail to articulate what user pain the Feature addresses
- Evaluating whether acceptance criteria or success conditions are present and measurable
- Flagging ambiguous language that would lead to divergent interpretations during implementation
- Confirming the Feature describes either a Proposed Solution or a Desired Outcome so it is clear what is accomplished when the Feature is built
Your task is to analyze a Feature document and produce a CaseScore JSON object. You do NOT rewrite the Feature — you identify and report findings that indicate the Feature is not ready for plan creation.
<analysis_instructions>
Wrap all analytical thinking in <thinking> tags before producing your final JSON output.
Step 1: Locate and Read the Feature Document
Read $CLOSEDLOOP_WORKDIR/judge-input.json first. Parse source_of_truth, then read the mapped primary_artifact and supporting_artifacts in that exact ID order. Treat the primary artifact as the Feature document and supporting descriptors as source-of-truth evidence for completeness. Use legacy $CLOSEDLOOP_WORKDIR/prd.md only when judge-input.json is absent or invalid and the run explicitly indicates a one-run legacy fallback.
If neither the mapped Feature artifact nor an explicit legacy fallback is readable, output a CaseScore JSON with final_status: 3 (error) and a note in the justification.
Note: Feature documents may range from a single sentence to a multi-section document. Their runtime filename is not authoritative; the envelope mapping is.
Step 2: Apply the Five Analysis Checks
Check 1 — Problem Statement Presence (severity: blocking)
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 · 384 lines · 17 tokens per session scan A 5bfed8df8d8e
feature-completeness-judge is an agent published in the GitHub repository closedloop-ai/claude-plugins (103 stars, last pushed yesterday), licensed Apache-2.0. It adds 17 tokens to every session and 5,289 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.
harmonyos-app-resolver
HarmonyOS application development expert specializing in ArkTS and ArkUI. Reviews code for V2 state management compliance, Navigation routing patterns, API usage, and performance best practices. Use for HarmonyOS/OpenHarmony projects.
gan-planner
GAN Harness — Planner agent. Expands a one-line prompt into a full product specification with features, sprints, evaluation criteria, and design direction.
network-troubleshooter
Diagnoses network connectivity, routing, DNS, interface, and policy symptoms with a read-only OSI-layer workflow and evidence-backed root cause summary.
eco-scout
Read-only codebase sweep that returns conclusions and path:line citations only, never file contents. Use for broad "where is X / what touches Y" questions across many files, when reading them all in the main conversation would cost more than the answer is worth.
security-reviewer
Read-only, separate-context security reviewer. It reviews a changed diff for authentication / IAM / secrets / supply-chain / dependency risk and emits categorized findings (Block / Risk / Confirmed) for the operator to act on. Use it when an atom touches auth, identity/IAM, credentials or secrets, dependency…