render-audit

A quality checker for finished web pages that inspects the page as it appears in a browser. It checks layout measurements, color contrast, visible scene coverage, and screenshots across screen sizes and light or dark themes.

In plain words
What is it for?
Use it to audit frontend pages before declaring them finished and report findings with evidence and severity levels.
Why use it?
It finds problems that may be missed when reviewing only HTML, CSS, or source code.

Plugin for Claude Code

Install

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.

Claude Code
/plugin marketplace add laguna821/Achmage-Skills
agentmods
npx agentmods add plugins/laguna821/achmage-skills/render-audit
Clone the repo
git clone --depth 1 https://github.com/laguna821/Achmage-Skills

Made for: Claude Code.

Per session not measured What this adds to a session before it is invoked.
When invoked not measured Not applicable: nothing here is loaded into a session.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Security

Grade A, and why

render-audit 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 2d 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.

Design-Consulting/render-audit/.claude-plugin/plugin.json · 12 lines

What it actually says

{
  "name": "render-audit",
  "description": "Render-measured QA auditor for built frontend pages. Runs four layers against the RENDERED page, never just the source: RQ1 deterministic structure checks (9 items, getBoundingClientRect), RQ2 pixel-contrast measurement (canvas worst-pixel WCAG), RQ2-OBS scene observability & coverage accounting (texture-energy sd — the dual pull that stops scrim monotone escalation), RQ3 multimodal screenshot traversal with a mandatory section×scheme matrix. FULL sweep (3 widths × 2 schemes) is the default; reduced runs are legal only by explicit declaration. Findings follow audit discipline: HIGH/MED/LOW severity, evidence-not-taste, cap 15, honest Not-reviewed listing. Pairs with component-consulting-v3's Render QA hand-off contract, but audits any frontend build.",
  "version": "1.0.1",
  "author": {
    "name": "laguna821"
  },
  "homepage": "https://github.com/laguna821/Achmage-Skills/tree/main/Design-Consulting/render-audit",
  "license": "MIT",
  "keywords": ["skill", "qa", "render-audit", "accessibility", "contrast", "frontend", "design-consulting", "claude-code"]
}
Changes

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.

  1. 2d ago First seen · 12 lines scan A 68a84fefb4c2

Subscribe to this mod's changes

render-audit is a plugin published in the GitHub repository laguna821/Achmage-Skills (5 stars, last pushed 3d ago), licensed Apache-2.0. Its token cost is not measured: this kind of file is read by the harness, not the model. 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.