pwa-audit

pwa-audit is a command for Claude Code from acaprino/daodan. It costs 45 tokens per session (2,153 once invoked), scanned A, original, MIT.

A PWA audit command for checking a progressive web app, which is a website designed to install and work more like an app.

In plain words
What is it for?
Use it to inspect a local PWA codebase or a deployed website's manifest, service worker, install requirements, offline behavior, security headers, and Core Web Vitals.
Why use it?
It finds installation, offline, security-header, and performance problems that can keep a PWA from being reliable or production-ready. It cites the relevant file and line for local projects, or checks a live URL.

Command for Claude Code

Written for Claude Code: argument-hint in frontmatter. Also seen: names the AskUserQuestion tool.

Part of the pwa-expert plugin — 1 skill, 3 commands, 1 agent shipped together

Good fit Use it to inspect a local PWA codebase or a deployed website's manifest, service worker, install requirements, offline behavior, security headers, and Core Web Vitals.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/acaprino/daodan/pwa-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/acaprino/daodan

Made for: Claude Code.

Or install pwa-expert, the plugin that ships this one along with the rest of its 1 skill, 3 commands, 1 agent.

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 pwa-audit

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

Your own site · 80×15
<a href="https://agentmods.dev/commands/acaprino/daodan/pwa-audit"><img src="https://agentmods.dev/badge/commands/acaprino/daodan/pwa-audit.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 45 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 2,153 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 1 finding. 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.00045 $0.02153
Opus 5 $0.00023 $0.01077
Sonnet 5 $0.00009 $0.00431
Haiku 4.5 $0.00005 $0.00215

Measured 4d ago against content hash ffc7a584bb43, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

pwa-audit scanned grade A 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 4d 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.

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

- A service worker fetch handler that calls `event.respondWith(fetch(event.request))` unconditionally. Adds latency for zero caching benefit.
exports/claude/plugins/pwa-expert/commands/pwa-audit.md · 135 lines

How it starts

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

/pwa-expert:pwa-audit

Adversarial PWA audit. Two modes, auto-detected from $ARGUMENTS:

  • Live URL mode: if the argument starts with http:// or https://, fetch the page with Playwright, parse the manifest, test install criteria, check security headers, test offline behavior, and measure Core Web Vitals on the landing page.
  • Local code mode: otherwise, treat the argument as a path (default: current working directory). Locate the manifest file, service worker source, registration call, iOS meta tag block, and security-header configuration in the codebase. Parse and check.

Setup

Delegate this audit to the pwa-architect agent. The agent must read the relevant references from the pwa-development skill on-demand (not all upfront), targeting each section of the audit.

Reference reading order, as audit sections are reached:

  • Manifest checks: references/manifest.md, references/production-checklist.md §1.
  • Install criteria and prompts: references/install-flows.md.
  • Service worker logic: references/service-workers.md.
  • Security headers: references/security.md.
  • Offline behavior: references/service-workers.md and references/storage-persistence.md.
  • Performance metrics: references/performance.md.
  • Push notifications: references/push-notifications.md.
  • Framework-specific files: references/frameworks-tooling.md.

Mode A: Live URL

If $ARGUMENTS is a URL, use the playwright-skill tools:

  1. Launch a browser and navigate to the URL.
  2. Fetch /manifest.webmanifest (and fall back to /manifest.json). Validate as JSON. Run the manifest checklist from production-checklist.md §1.
  3. Check the service worker registration: look for a <script> registering navigator.serviceWorker.register(...), or for an existing controller via navigator.serviceWorker.controller.
  4. Check the install criteria from install-flows.md: manifest valid, display not browser, SW registered with fetch handler, HTTPS, 192+512 PNG icons present.
  5. Check meta tags: apple-mobile-web-app-capable, apple-mobile-web-app-status-bar-style, apple-mobile-web-app-title, apple-touch-icon, theme-color, viewport.
  6. Check security headers via response headers: HTTPS plus HSTS, CSP presence (warn if 'unsafe-eval' is allowed), Cross-Origin-Opener-Policy, Cross-Origin-Embedder-Policy.
  7. Test offline behavior: route the page through page.context().setOffline(true), reload, and confirm a non-broken response (offline page or cached navigation).
  8. Measure Core Web Vitals on the landing page (LCP, CLS at least; INP requires interaction). Compare against performance.md thresholds.

Read the full file on GitHub · 135 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. 4d ago First seen · 135 lines · 45 tokens per session scan A ffc7a584bb43

Subscribe to this mod's changes

pwa-audit is a command published in the GitHub repository acaprino/daodan (9 stars, last pushed yesterday), licensed MIT. It adds 45 tokens to every session and 2,153 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-05.