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.
npx agentmods add commands/oalders/kitchen-sink/responsive-auditgit clone --depth 1 https://github.com/oalders/kitchen-sinkWrote 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/commands/oalders/kitchen-sink/responsive-audit)<a href="https://agentmods.dev/commands/oalders/kitchen-sink/responsive-audit"><img src="https://agentmods.dev/badge/commands/oalders/kitchen-sink/responsive-audit.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 | $0.00021 | $0.02614 |
| Opus 5 | $0.00010 | $0.01307 |
| Sonnet 5 | $0.00004 | $0.00523 |
| Haiku 4.5 | $0.00002 | $0.00261 |
Grade B, and why
responsive-audit scanned grade B with 1 finding 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 5d 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.
Cloud metadata endpointmediumServer-side request forgery
One request to 169.254.169.254 can return temporary IAM credentials.
address (`169.254.0.0/16`, `[fd00:ec2::254]`, `metadata.google.internal`, etc.); for any host that Downgraded: this mod is about security review, or the phrase is quoted, so it is likely naming the pattern rather than instructing it.
How it starts
The opening of the file, as written. The whole thing — 198 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Responsive Audit
Overview
Live-discovery responsive audit: drives the Playwright MCP to load one or more
already-serving URLs at several viewport widths and reports responsive breakage that
static review can't see. It fills the gap between /frontend-review (which reasons about a
source diff and only recommends manual screenshots) and /playwright-review (which
reviews existing test source) — neither actually drives a browser against a live page.
Discovery/reporting only: no test files are written, no source is modified, and no dev server is started.
Deliberate departure from the sibling review commands: the steps below drive the
Playwright MCP tools directly (navigate, resize, evaluate JS, screenshot) rather than
spawning a Task(general-purpose) subagent the way /frontend-review and
/playwright-review do. There is a live browser session to hold, so the work stays in the
caller's context and ## Output Format is a top-level section (no subagent to nest it in).
This inconsistency is intentional.
Hard prerequisite: a working Playwright MCP must be available in the session. The command cannot probe tool availability up front — if the MCP is absent it simply fails on the first browser call. State the prerequisite before starting and surface that failure clearly rather than pretending to detect it. The target URL(s) must already be reachable.
When to Use
Use when:
- You have a live, already-serving page and want to find responsive layout breakage across viewport widths (overflow, occluded controls, tiny touch targets / text).
- You want measured evidence plus full-page screenshots, not just a reasoned guess from a diff.
- A
/frontend-reviewflagged possible responsive risk and you want to confirm it on the real page.
Don't use when:
- The page isn't serving yet — this command does not start a dev server (start it yourself first).
- You want a source-diff review (use
/frontend-review) or a review of Playwright test source (use/playwright-review). - You want tests written, source auto-fixed, or issues/PRs filed — all explicit non-goals.
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.
- 5d ago First seen · 198 lines · 21 tokens per session scan B d4e7bd51bbbb
responsive-audit is a command published in the GitHub repository oalders/kitchen-sink (4 stars, last pushed 5d ago), licensed MIT. It adds 21 tokens to every session and 2,614 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it B with 1 finding (cloud metadata endpoint). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other commands, from other repositories
auto-browse
Auto-browse — learn, optimize, and graduate browser operations or web data-mining workflows.
ccboard-web
Launch ccboard web interface.
webapp-testing
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.
gh-issue-use-cypress
Like /gh-issue-use-browser, but pinned to the Cypress MCP — use when your project runs the Cypress MCP for browser automation. Example — /gh-issue-use-cypress "Composer > Save" saving toasts failure but the record persists.
responsive-design-specialist
Use when a layout breaks between sizes. Arbitrary breakpoints, type that does not scale, images that blow out the grid, or a desktop design retrofitted onto mobile.
wcag-audit
Accessibility audit based on WCAG 2.1/2.2 and the axe-core reference.