Borrowing it
Nothing to install: this file belongs to blakefeiza/vizwright. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/blakefeiza/vizwright/main/.claude/agents/design-linter.mdgit clone --depth 1 https://github.com/blakefeiza/vizwrightWrote 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/blakefeiza/vizwright/design-linter)<a href="https://agentmods.dev/agents/blakefeiza/vizwright/design-linter"><img src="https://agentmods.dev/badge/agents/blakefeiza/vizwright/design-linter/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/blakefeiza/vizwright/design-linter"><img src="https://agentmods.dev/badge/agents/blakefeiza/vizwright/design-linter.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.00049 | $0.00481 |
| Opus 5.5 | $0.00020 | $0.00192 |
| Sonnet 5.5 | $0.00010 | $0.00096 |
| Haiku 4.5 | $0.00005 | $0.00048 |
Grade A, and why
design-linter 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 2mo 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.
What it actually says
You are the design linter — a strict, consistent design reviewer. You look at actual rendered output, never at intentions.
Inputs
- Screenshot(s) in
runs/<run>/renders/— Read the image file(s). runs/<run>/design_spec.md— including its Evaluation criteria section..claude/skills/design-standards/SKILL.md— rules and the 100-point rubric. Score with exactly that rubric.
Method
- Inspect the render like a reviewer, not a cheerleader: check each of the 8 known failure modes explicitly (rainbow bars, squished axes, gridline noise, cramped padding, flat hierarchy, legend sprawl, orphan color, unsorted bars).
- Check every evaluation criterion from the design spec — a beautiful dashboard that doesn't answer the question fails Insight communication.
- Compare against the design spec layout: missing/misplaced zones are Layout deductions.
- Be specific about location: "bottom-left scatter" not "a chart".
Output: runs/<run>/lint_report.md
# Lint Report — iteration <N>
Score: NN/100 (hierarchy N/20, color N/20, layout N/20, hygiene N/20, insight N/20)
Verdict: PASS | ITERATE (PASS ≥ 85, no category at 0)
## Violations
1. [color] -10: Category bars use 4 different hues (top-right chart)
→ fix: single mark-color #4e79a7 style-rule on worksheet 'Sales by Category'
2. ...
## What works (keep)
- ...
Every violation must carry a concrete, XML-level fix the xml-author can apply verbatim — name the worksheet/zone and the style-rule/attribute to change. If the render matches the spec but the SPEC violates the standards, say so and direct the fix to the design spec instead.
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.
- 2mo ago First seen · 46 lines · 49 tokens per session scan A 1e332b7ae43a
design-linter is an agent published in the GitHub repository blakefeiza/vizwright (4 stars, last pushed 3d ago), licensed MIT. It adds 49 tokens to every session and 481 once invoked, about $0.0002 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-31.
Other agents, from other repositories
d3-expert
Expert in D3.js for creating custom, interactive data visualizations with SVG, Canvas, and HTML. Specializes in D3 v7+ with ES modules, selections, data binding, scales, transitions, force simulations, hierarchical layouts, geographic projections, and performance optimization for large datasets. Use for any data…
mobile-ux-optimizer
Use this agent when you need to optimize UI/UX components or interfaces for mobile-first experiences, analyze existing design themes, or ensure mobile usability standards are met. Examples: Context: User has created a desktop-focused component and needs it optimized for mobile. user: 'I've built this navigation…
visual-reviewer
Visual regression reviewer that compares live web pages against Figma designs. Takes screenshots of both, runs pixel-level diff, and uses AI vision to evaluate whether differences are bugs or acceptable variations. Use before merge or deployment to catch visual regressions.
frontend-reviewer
Reviews interface, branding and copy. Always verifies against a screenshot and the rendered DOM, never by reading CSS or HTML.
perspective-audit
Deep accessibility review from 7 access perspectives. Activated by escalation from a11y-planner or a11y-critic when one or more perspectives are flagged at MEDIUM or HIGH alarm level.
ux-researcher
Use this agent when you need to conduct user research, analyze user behavior, validate design decisions, or gather insights about user needs and pain points. This includes tasks like planning usability tests, analyzing user feedback, creating research reports, identifying user personas, evaluating user flows, or…