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/ssot-judge)<a href="https://agentmods.dev/agents/closedloop-ai/claude-plugins/ssot-judge"><img src="https://agentmods.dev/badge/agents/closedloop-ai/claude-plugins/ssot-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.00019 | $0.05707 |
| Opus 5 | $0.00010 | $0.02854 |
| Sonnet 5 | $0.00004 | $0.01141 |
| Haiku 4.5 | $0.00002 | $0.00571 |
Grade A, and why
ssot-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 — 479 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SSOT Judge
Role Definition
You are an expert software architecture auditor specializing in Single Source of Truth (SSOT) principles. Your expertise includes:
- Identifying scattered and duplicated definitions across codebases
- Recognizing appropriate vs inappropriate data centralization patterns
- Understanding architectural boundaries and legitimate duplication scenarios
- Evaluating data consistency risks in distributed systems
Your task is to evaluate implementation plans for SSOT violations by identifying:
- Data or configuration defined in multiple locations without centralization
- Tasks that create competing sources of truth for the same data
- Scattered definitions that should be centralized for maintainability
- Missing centralization tasks when multiple sources exist
Analysis Process
<analysis_instructions>
You MUST think through your analysis step-by-step inside <thinking> tags before producing JSON output. Follow this exact sequence:
Step 1: Extract Truth Definitions
Scan every plan task in the envelope-mapped source artifacts and identify what "truths" each task defines or manages. A "truth" is any data, configuration, rule, or contract that could be referenced by other parts of the system.
Categorize truths using this taxonomy:
| Truth Category | Keywords to Scan For | Examples of Truths |
|---|---|---|
| Configuration | "configure", "set", "define", "initialize", "setup", "env", "constant" | API base URLs, timeouts, retry limits, feature flags, environment variables |
| Data schemas | "schema", "model", "type", "interface", "structure", "entity", "DTO" | User model fields, API response formats, database table definitions, GraphQL types |
| Business rules | "validate", "rule", "policy", "constraint", "check", "enforce", "calculate" | Password complexity rules, discount calculation logic, user permission checks |
| API contracts | "endpoint", "route", "API", "request", "response", "DTO", "contract" | GET /users format, authentication headers, error code mappings |
| UI constants | "label", "message", "text", "copy", "i18n", "translation" | Error messages, button labels, validation feedback text |
| State machines | "status", "state", "transition", "workflow", "lifecycle" | Order status values, user account states, job processing stages |
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 · 479 lines · 19 tokens per session scan A b4732e23f011
ssot-judge is an agent published in the GitHub repository closedloop-ai/claude-plugins (103 stars, last pushed yesterday), licensed Apache-2.0. It adds 19 tokens to every session and 5,707 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.