responsive-audit

responsive-audit is a command for Claude Code from sigistry/marketplace. It costs 19 tokens per session (3,152 once invoked), scanned A, original, MIT.

A read-only check of a website's source code for problems that affect phones and tablets. It produces findings with a severity and a blast radius, meaning whether a fix could also change the desktop layout.

In plain words
What is it for?
Use it to inspect HTML, CSS, and framework components for fixed widths, horizontal overflow, missing viewport settings, small touch targets, and missing media-query behavior.
Why use it?
It identifies likely responsive design problems before deployment without editing files. Because it reads source rather than rendering the site on a device, it cannot replace real-device or emulator testing.

Command for Claude Code

Written for Claude Code: argument-hint in frontmatter. Also seen: model in frontmatter.

Part of the responsive-design-kit plugin — 1 skill, 2 commands shipped together

Good fit Use it to inspect HTML, CSS, and framework components for fixed widths, horizontal overflow, missing viewport settings, small touch targets, and missing media-query behavior.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/sigistry/marketplace/responsive-audit
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.

Clone the repo
git clone --depth 1 https://github.com/sigistry/marketplace

Made for: Claude Code.

Or install responsive-design-kit, the plugin that ships this one along with the rest of its 1 skill, 2 commands.

Wrote 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.

agentmods badge for responsive-audit

README.md
[![agentmods](https://agentmods.dev/badge/commands/sigistry/marketplace/responsive-audit/github.svg)](https://agentmods.dev/commands/sigistry/marketplace/responsive-audit)
Your own site
<a href="https://agentmods.dev/commands/sigistry/marketplace/responsive-audit"><img src="https://agentmods.dev/badge/commands/sigistry/marketplace/responsive-audit/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.

agentmods 80×15 button for responsive-audit

Your own site · 80×15
<a href="https://agentmods.dev/commands/sigistry/marketplace/responsive-audit"><img src="https://agentmods.dev/badge/commands/sigistry/marketplace/responsive-audit.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 19 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 3,152 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00019 $0.03152
Opus 5.5 $0.00008 $0.01261
Sonnet 5.5 $0.00004 $0.00630
Haiku 4.5 $0.00002 $0.00315

Measured 1mo ago against content hash 6a237fb3aa9a, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

responsive-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 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.

plugins/responsive-design-kit/commands/responsive-audit.md · 213 lines

How it starts

The opening of the file, as written. The whole thing — 213 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Responsive Design Audit

You are a Responsive Design Auditor. Your task is to assess how well the provided source renders on phones and tablets, working from the code rather than a live render. Produce a scored report where every finding carries a severity and a blast radius: whether fixing it touches only small screens or could change the desktop layout too.

This is a read-only assessment. Do not edit files. The companion /responsive-fix command applies the changes.

What "from source" means (and its limits)

You read HTML, CSS, and framework components to find responsiveness problems before deployment, the same way a linter finds bugs without running the program. This catches the large majority of real issues (missing viewport, fixed widths, overflow, small tap targets, media-query gaps). It does not replace testing on a real device or emulator, some issues only appear at a specific viewport width with real content. Say so in the report. Never claim a page "is responsive", only that the source is free of the issues you check for.

The blast-radius model

Every finding gets one of these labels. It is the single most useful thing in the report, because it tells the reader how risky the fix is.

  • Additive (safe): the fix adds a property that has no effect on the current desktop rendering and only kicks in on small screens or overflow. Example: adding the viewport meta tag, max-width: 100% on an image, an overflow-x: auto wrapper on a wide table. Apply freely.
  • Mobile-only (safe): the fix lives inside a max-width media query (or a container query), so desktop is untouched by construction. Example: stacking a flex row below 640px. Apply freely.
  • Shared (caution): the fix changes a value that applies at all breakpoints, so it changes desktop too. Example: replacing width: 960px with max-width: 960px; width: 100%. Usually correct, but must be eyeballed on desktop.
  • Structural (high-risk): the fix reflows the layout, changes the markup, or swaps the positioning model. Example: converting a fixed three-column grid to auto-fit, or restructuring a data table into stacked cards. Needs deliberate review and testing.

Read the full file on GitHub · 213 lines

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. 1mo ago First seen · 213 lines · 19 tokens per session scan A 6a237fb3aa9a

Subscribe to this mod's changes

responsive-audit is a command published in the GitHub repository sigistry/marketplace (3 stars, last pushed 3d ago), licensed MIT. It adds 19 tokens to every session and 3,152 once invoked, about $0.0001 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-09-10.