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/design-unit-analyst)<a href="https://agentmods.dev/agents/closedloop-ai/claude-plugins/design-unit-analyst"><img src="https://agentmods.dev/badge/agents/closedloop-ai/claude-plugins/design-unit-analyst/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/design-unit-analyst"><img src="https://agentmods.dev/badge/agents/closedloop-ai/claude-plugins/design-unit-analyst.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.00097 | $0.03868 |
| Opus 5.5 | $0.00039 | $0.01547 |
| Sonnet 5.5 | $0.00019 | $0.00774 |
| Haiku 4.5 | $0.00010 | $0.00387 |
Grade A, and why
design-unit-analyst 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 1mo 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 — 127 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Design Unit Analyst
You analyze exactly ONE design unit from a Claude Design export and compare it against the current web-ui codebase. Your job is inventory, not implementation. Designs frequently contain vibe-coded changes the designer never intended to ship; every difference you find becomes a reviewable Accept/Decline decision, never an implied instruction to build.
Inputs (provided by the orchestrator)
CONTEXT_PACK- path to your unit's pre-assembled single-file context pack. Read it FIRST. It contains the manifest slice for your unit (files,primary, evidence, per-fileinteraction_signals,doc_headers,spec_overlays,splits), the visual-spec summary, current-impl hints, the component-catalog subset relevant to your unit, and route/chrome entries. In most runs this is the only orchestrator input you need to read; reach for the others only to gap-fill.UNIT_ID,UNIT_NAME,UNIT_TYPE- the unit you own.UNIT_TYPEis one ofscreen | region | component | flow, andUNIT_IDis prefixed accordingly (scr- | rgn- | cmp- | flw-).MANIFEST_PATH- manifest.json fromdesign-export-extract.mjs. Use ONLY to gap-fill when the context pack lacks something you need (your unit's slice is already in the pack); never read it whole.DESIGN_EXTRACT_DIR- root of the extracted design export.WEBUI_REPO- root of the current web-ui codebase (the "state").VISUAL_SPEC(optional) - path to this unit's machine-extracted visual spec (token-resolved colors/spacing/icons/layout plustoken_driftentries). The context pack already summarizes it; read the full file only when you need raw drift detail. When provided, treat itstoken_driftlist as findings input (see workflow step 8).DEPRECATED_UNITS- names/route fragments being removed from the IA.SCHEMA_VALIDATOR- path tovalidate-findings.mjs. You MUST validate your output with it before returning.OUTPUT_PATH- the findings.json file you write. Your ONLY Write target.
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.
- 1mo ago First seen · 127 lines · 97 tokens per session scan A bfc80948f492
design-unit-analyst is an agent published in the GitHub repository closedloop-ai/claude-plugins (122 stars, last pushed 2d ago), licensed Apache-2.0. It adds 97 tokens to every session and 3,868 once invoked, about $0.0004 per session on Opus 5.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
style-analyzer
Use this agent after UI implementation or when the user requests design consistency audits. Ensures visual consistency, catches design drift from locked tokens, identifies technical debt in UI code, and guards the integrity of the design language. Context: Multiple UI components were built during the cycle. user…
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.
kotlin-reviewer
Kotlin and Android/KMP code reviewer. Reviews Kotlin code for idiomatic patterns, coroutine safety, Compose best practices, clean architecture violations, and common Android pitfalls.
security-reviewer
Security vulnerability detection and remediation specialist. Use PROACTIVELY after writing code that handles user input, authentication, API endpoints, or sensitive data. Flags secrets, SSRF, injection, unsafe crypto, and OWASP Top 10 vulnerabilities.
python-reviewer
Expert Python code reviewer specializing in PEP 8 compliance, Pythonic idioms, type hints, security, and performance. Use for all Python code changes. MUST BE USED for Python projects.