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.
git 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/commands/acaprino/daodan/pwa-checklist)<a href="https://agentmods.dev/commands/acaprino/daodan/pwa-checklist"><img src="https://agentmods.dev/badge/commands/acaprino/daodan/pwa-checklist/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/commands/acaprino/daodan/pwa-checklist"><img src="https://agentmods.dev/badge/commands/acaprino/daodan/pwa-checklist.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.00072 | $0.01002 |
| Opus 5 | $0.00036 | $0.00501 |
| Sonnet 5 | $0.00014 | $0.00200 |
| Haiku 4.5 | $0.00007 | $0.00100 |
Grade A, and why
pwa-checklist 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 3d 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 — 104 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/pwa-expert:pwa-checklist
Walk the production deploy checklist from references/production-checklist.md interactively against the current project (or the provided URL).
Delegate to pwa-architect. The agent reads production-checklist.md upfront (this is one of the few cases where preloading a reference is correct, because the command IS the checklist), then walks every item.
Modes
- If
$ARGUMENTSis a URL: walk the checklist against the live deployment viaplaywright-skillwhere applicable, plus the codebase for items that can only be verified in source. - If
$ARGUMENTSis a path or omitted: walk against the codebase only.
How the walk works
For every item in every category of production-checklist.md:
- State the item verbatim.
- Verify it. Use
Read,Grep,Glob,Bash, orplaywright-skilltools as appropriate. - Record the result as one of: PASS, FAIL, N/A (with a reason for N/A).
Output format
Produce a markdown report:
# Production Checklist Report
**Target:** <path or URL>
**Date:** YYYY-MM-DD
## Summary
| Category | Pass | Fail | N/A | Score |
|---|---|---|---|---|
| Manifest | X | Y | Z | X / (X+Y) |
| iOS-specific | ... |
| Service Worker | ... |
| Security | ... |
| Performance | ... |
| Push | ... |
| Storage | ... |
| Testing | ... |
| Distribution | ... |
| Monitoring | ... |
| **Overall** | ... |
## Manifest
- [PASS] id is explicit (not implied from start_url). Found in `public/manifest.webmanifest:2`.
- [FAIL] Icons: 192 PNG purpose: "maskable" missing. Add via /pwa-expert:pwa-scaffold or by hand.
- ...
(... and so on for every category, every item)
## Recommended next actions
(Numbered list of the highest-impact fails, ordered by severity.)
Difference from /pwa-expert:pwa-audit
pwa-auditis open-ended and adversarial. It uses domain knowledge to find defects the checklist does not enumerate.pwa-checklistis deterministic. The output maps 1:1 to the source guide's deploy checklist sections. Two runs on the same target produce structurally identical reports.
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.
- 3d ago First seen · 104 lines · 72 tokens per session scan A cbaa09dd467c
pwa-checklist is a command published in the GitHub repository acaprino/daodan (9 stars, last pushed today), licensed MIT. It adds 72 tokens to every session and 1,002 once invoked, about $0.0004 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 commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.