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 skills add acaprino/daodan --skill pwa-developmentgit clone --depth 1 https://github.com/acaprino/daodanWrote 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/skills/acaprino/daodan/pwa-development)<a href="https://agentmods.dev/skills/acaprino/daodan/pwa-development"><img src="https://agentmods.dev/badge/skills/acaprino/daodan/pwa-development/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/skills/acaprino/daodan/pwa-development"><img src="https://agentmods.dev/badge/skills/acaprino/daodan/pwa-development.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.00147 | $0.01217 |
| Opus 5 | $0.00073 | $0.00609 |
| Sonnet 5 | $0.00029 | $0.00243 |
| Haiku 4.5 | $0.00015 | $0.00122 |
Grade A, and why
pwa-development 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 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.
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.
How it starts
The opening of the file, as written. The whole thing — 66 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Progressive Web App Development
Knowledge base for building, auditing, and shipping Progressive Web Apps in 2025-2026. Covers manifest, service workers, Web Push, install flows, storage, Project Fugu capabilities, platform constraints, performance (Core Web Vitals), security, and distribution to Google Play, Microsoft Store, App Store (via Capacitor), and Meta Quest.
When to use this skill
Use this skill whenever the active task involves any of:
- A
manifest.webmanifestormanifest.json, manifest members, icons, splash screens, iOS meta tags. - A service worker file, registration, caching strategy, update flow, Workbox 7, Serwist.
- Web Push: VAPID keys, subscription, server-side delivery, Declarative Web Push.
- PWA install flow on Chromium (
beforeinstallprompt), iOS (manual), or Window Controls Overlay on desktop. - Background execution: Background Sync, Periodic Background Sync, Background Fetch, Screen Wake Lock.
- Storage: IndexedDB, OPFS, quotas,
navigator.storage.persist(). - Project Fugu APIs: File System Access, Web Share, Web Bluetooth / USB / HID / Serial / NFC, WebAuthn, etc.
- Performance for PWAs: Core Web Vitals 2025, INP < 200ms, app shell, code splitting.
- Security headers for PWAs: HTTPS, CSP tuned for SW, COOP / COEP for
SharedArrayBuffer. - Distribution: Bubblewrap to Google Play (TWA +
assetlinks.json), PWA Builder to Microsoft Store (MSIX), Capacitor to App Store, PWA Builder to Meta Quest. - Framework integration: Vite (
vite-plugin-pwa), Next.js (@serwist/next), Angular (ng add @angular/pwa), Nuxt (@vite-pwa/nuxt).
Skip this skill if the task is generic frontend styling, generic React performance, cross-platform security unrelated to PWA mechanics, Tauri or Electron wrappers, or GA4 / analytics.
References Library
Read the relevant reference on-demand for the active task. Do NOT preload all references at once; pick the one that matches the question.
| Reference | Topic |
|---|---|
references/manifest.md |
Web App Manifest: members, icons, splash, iOS meta tags |
references/service-workers.md |
SW lifecycle, caching strategies, Workbox 7, updates, debugging |
references/background-execution.md |
Background Sync, Periodic Sync, Background Fetch, Wake Lock |
references/push-notifications.md |
Web Push end-to-end: VAPID, RFCs, Declarative Push, Badge API |
references/install-flows.md |
beforeinstallprompt, iOS manual install, Window Controls Overlay |
references/permissions.md |
Permissions API, Permissions-Policy header, platform availability |
references/storage-persistence.md |
IndexedDB, OPFS, quotas, persistent storage |
references/capabilities-fugu.md |
Project Fugu API matrix and worked examples |
references/platform-constraints.md |
iOS / Android / Desktop per-platform reality check |
references/performance.md |
Core Web Vitals 2025, INP < 200ms, audit tooling |
references/security.md |
HTTPS, CSP for SW, COOP / COEP, secure contexts |
references/distribution.md |
Bubblewrap / TWA, PWA Builder MSIX, Capacitor, Meta Quest |
references/frameworks-tooling.md |
Vite, Next.js, Angular, Nuxt + debugging surface |
references/production-checklist.md |
Full deploy checklist for going to production |
What ships with it
14 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- references/background-execution.md 18 KB
- references/capabilities-fugu.md 16 KB
- references/distribution.md 17 KB
- references/frameworks-tooling.md 23 KB
- references/install-flows.md 18 KB
- references/manifest.md 37 KB
- references/performance.md 14 KB
- references/permissions.md 17 KB
- references/platform-constraints.md 30 KB
- references/production-checklist.md 5.5 KB
- references/push-notifications.md 33 KB
- references/security.md 17 KB
- references/service-workers.md 36 KB
- references/storage-persistence.md 28 KB
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.
- 4d ago First seen · 66 lines · 147 tokens per session scan A 26572dca03d7
pwa-development is a skill published in the GitHub repository acaprino/daodan (9 stars, last pushed yesterday), licensed MIT. It adds 147 tokens to every session and 1,217 once invoked, about $0.0007 per session on Opus 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-05.
Other skills, from other repositories
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
next-dev-loop
Verify Next.js runtime behavior after editing app code. Use this skill to confirm a change actually works in a running app — not just that it compiles or type-checks. Combines /next/mcp (Next.js's view) with agent-browser (the browser's view). Requires a running next dev.
playwright-component-testing
Set up component testing with Playwright using a story gallery — scaffold stories and a gallery dev page driven by the built-in mount fixture, no dedicated component-testing runtime. Use when asked to test React or Vue components in isolation with Playwright, or to migrate off @playwright/experimental-ct-react / -vue.
a11y-debugging
Uses Chrome DevTools MCP for accessibility (a11y) debugging and auditing based on web.dev guidelines. Use when testing semantic HTML, ARIA labels, focus states, keyboard navigation, tap targets, and color contrast.