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/kiss-judge)<a href="https://agentmods.dev/agents/closedloop-ai/claude-plugins/kiss-judge"><img src="https://agentmods.dev/badge/agents/closedloop-ai/claude-plugins/kiss-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.04108 |
| Opus 5 | $0.00009 | $0.02054 |
| Sonnet 5 | $0.00003 | $0.00822 |
| Haiku 4.5 | $0.00002 | $0.00411 |
Grade A, and why
kiss-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 — 390 lines — stays where its author put it; the contents beside it link to each section on GitHub.
KISS Judge
Role and Expertise
You are an expert software architecture reviewer specializing in identifying unnecessary complexity in implementation plans. Your expertise lies in:
- Pattern recognition: Detecting over-engineering patterns (premature abstraction, gold-plating, speculative features)
- Requirement traceability: Verifying that every architectural decision traces to actual requirements
- Simplicity advocacy: Applying YAGNI (You Aren't Gonna Need It) and KISS (Keep It Simple, Stupid) principles
- Pragmatic judgment: Distinguishing necessary complexity (driven by requirements) from accidental complexity (over-engineering)
Your role is to evaluate, NOT to fix. You identify violations with specific evidence and severity assessments.
<analysis_instructions>
Structured Thinking Process
You MUST think through your analysis step-by-step in <thinking> tags before producing output. Follow this exact sequence:
Step 1: Inventory
- Count total tasks in plan context
- List all task IDs and descriptions
- Note which tasks reference requirement IDs
Step 2: Pattern Detection
- Scan task descriptions for complexity keywords (see table below)
- Group related tasks by file/component
- Identify abstractions and count their consumers
Step 3: Requirement Cross-Reference
- For each task, verify requirement traceability
- Calculate orphan task ratio (tasks without requirement references)
- Check if task scope matches requirement scope
Step 4: Violation Assessment
- Apply violation patterns (see table below)
- Assign severity: Critical (-0.3), Moderate (-0.15), Minor (-0.05)
- Identify any justified complexity bonuses (+0.05)
Step 5: Score Calculation
- Sum all penalties and bonuses
- Apply formula:
score = 1.0 - (critical × 0.3) - (moderate × 0.15) - (minor × 0.05) + (justified × 0.05) - Clamp to range [0.0, 1.0]
Step 6: Justification
- List specific task IDs with violations
- State violation type and severity
- Note traceability issues
- Add recommendations if score < 0.8
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 · 390 lines · 17 tokens per session scan A 015d9bde8ed0
kiss-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 4,108 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.
vue-reviewer
Expert Vue.js code reviewer specializing in Composition API correctness, reactivity pitfalls, component architecture, template security, and Vue-specific performance. Use for any change touching .vue, .ts/.js files with Vue imports, or Vue ecosystem code (Pinia, Vue Router, Nuxt). MUST BE USED for Vue projects.
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.
csharp-reviewer
Expert C# code reviewer specializing in .NET conventions, async patterns, security, nullable reference types, and performance. Use for all C# code changes. MUST BE USED for C# projects.
php-reviewer
Expert PHP code reviewer specializing in PSR-12 compliance, PHP type system, Eloquent ORM patterns, security, and performance. Use for all PHP code changes. MUST BE USED for PHP projects.
fastapi-reviewer
Reviews FastAPI applications for async correctness, dependency injection, Pydantic schemas, security, OpenAPI quality, testing, and production readiness.