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 aiatelie/ai-atelie --skill verify-with-playwrightgit clone --depth 1 https://github.com/aiatelie/ai-atelieWrote 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/aiatelie/ai-atelie/verify-with-playwright)<a href="https://agentmods.dev/skills/aiatelie/ai-atelie/verify-with-playwright"><img src="https://agentmods.dev/badge/skills/aiatelie/ai-atelie/verify-with-playwright/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/aiatelie/ai-atelie/verify-with-playwright"><img src="https://agentmods.dev/badge/skills/aiatelie/ai-atelie/verify-with-playwright.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.00088 | $0.03518 |
| Opus 5 | $0.00044 | $0.01759 |
| Sonnet 5 | $0.00018 | $0.00704 |
| Haiku 4.5 | $0.00009 | $0.00352 |
Grade C, and why
verify-with-playwright scanned grade C with 2 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 12d 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
ls -1t .evidence | tail -n +6 | xargs -I{} rm -rf ".evidence/{}" Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -sSf http://localhost:5173 > /dev/null && echo "up" || echo "down" How it starts
The opening of the file, as written. The whole thing — 223 lines — stays where its author put it; the contents beside it link to each section on GitHub.
verify-with-playwright
A contributor workflow for AI Atelie. Drives the local dev server with @playwright/test (runner mode, not MCP), produces a test-results/<spec>/ folder with video + screenshots + trace, then bundles the relevant files into .evidence/<run>/ for upload to a PR.
This skill is dev-time only. It does not load into adapter sessions spawned by the editor.
When to invoke
- After implementing any change that touches
web/, the iframe canvas, the chat surface, the editor toolbar, or any other user-visible behaviour. - When the
ship-taskorchestrator delegates verification. - When the user asks "does it actually work in the browser?" or "show me proof".
Skip when:
- The change is API-only with no observable surface (use
web/tests/test-*.mjsintegration tests instead). - The change is a doc-only or config-only edit.
Preflight (do this before writing any spec)
- Confirm the dev server is up. Run:
If down, STOP and tell the user: "Runcurl -sSf http://localhost:5173 > /dev/null && echo "up" || echo "down"bun run devin another terminal, then retry." Do NOT spawnbun run devfrom this skill — backgrounded dev servers leak across sessions and will clobber the user's own terminal. - Confirm Playwright is installed.
bunx playwright --versionshould printVersion 1.59.xor higher. If not, runbun add -D @playwright/test && bunx playwright install chromium. - Read
playwright.config.tsat repo root to confirm the test dir, baseURL, and artifact policy haven't drifted.
Workflow (paste this checklist into your reply and tick as you go)
- Preflight passed (dev server up, Playwright installed).
- Acceptance criteria identified. From the issue or the user's task description, list the user-observable properties that must hold. Example for #1 (live preview): "agent text deltas appear in iframe srcdoc within 500ms of arrival; full reload not required".
- Spec authored. Write
web/tests/e2e/<slug>.spec.ts. One scenario per file. Use role-based selectors. Each acceptance criterion → one or moreexpect(...)calls. - Spec runs.
bunx playwright test web/tests/e2e/<slug>.spec.ts --reporter=list. - Wait for the agent to FULLY COMPLETE before stopping the recording. This is the rule reviewers care about most — see "Evidence must show the post-completion state" below. A capture that ends mid-stream proves nothing.
- Capture the post-completion state explicitly. A final screenshot AFTER the busy/loading state clears AND the user-visible result is rendered. The reviewer must be able to see what the agent actually produced, not just that it was working.
- Evidence bundled. Copy
test-results/<slug>/video.webmand any*.pnginto.evidence/<ISO-timestamp>-<slug>/. - (Optional) headed run for video review.
--headedfor clearer screen recordings on visual changes. - Cleanup. Prune
.evidence/to keep only the last 5 run folders. - Report. Output the absolute paths of evidence artifacts so
ship-task(or the user) can attach them to the PR.
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.
- 12d ago First seen · 223 lines · 88 tokens per session scan C 0ebd2ae89a6f
verify-with-playwright is a skill published in the GitHub repository aiatelie/ai-atelie (8 stars, last pushed 3mo ago), licensed MIT. It adds 88 tokens to every session and 3,518 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it C with 2 findings (recursive force delete, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
pptx-html-fidelity-audit
Audit a python-pptx export against its source HTML deck, identify layout/content drift (footer overflow, cropped content, missing italic/em, lost styling, off-rhythm spacing), and re-export with strict footer-rail + cursor-flow layout discipline. Use this skill whenever the user has a .pptx that was generated from an…
test-browser
Run browser tests on pages affected by current PR or branch.
flow
Verify a code change end-to-end in the current worktree: identify what changed, run the relevant tests, get the app running, drive a browser over the affected areas, and report a verdict with screenshots. Generic across project types (Laravel/Herd, Node/bun, frontend, CLI, library). Use when the user wants to…
qprobe
QUESTPIE Probe — dev testing CLI for AI coding agents. Start servers, test APIs, control browsers via agent-browser, record and replay regression tests with zero tokens. Use when testing web apps, starting dev servers, reading logs, debugging errors, making API calls, checking browser console/network, or composing…
field-test
Exercise tools, resources, and prompts against a live HTTP server via MCP JSON-RPC over curl. Starts the server, surfaces the catalog, runs real and adversarial inputs, measures every call (bytes, token estimate, wall-clock) and weighs the catalog, and produces a tight report with concrete findings and numbered…
browse
Drive a real browser through Aside: open a page, read it, click through a flow, take screenshots, check console errors. (gstack).