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 skills/idavidov13/agentic-playwright/common-tasksnpx skills add idavidov13/agentic-playwright --skill common-tasksgit clone --depth 1 https://github.com/idavidov13/agentic-playwrightWrote 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/idavidov13/agentic-playwright/common-tasks)<a href="https://agentmods.dev/skills/idavidov13/agentic-playwright/common-tasks"><img src="https://agentmods.dev/badge/skills/idavidov13/agentic-playwright/common-tasks.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.00177 | $0.02319 |
| Opus 5 | $0.00088 | $0.01159 |
| Sonnet 5 | $0.00035 | $0.00464 |
| Haiku 4.5 | $0.00018 | $0.00232 |
Grade A, and why
common-tasks 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 — 111 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AI Prompt Templates for Agentic Playwright
Codegen sub-router. Owns prompt templates per artifact type and the post-generation verification checklist. Plugs into ai-native-workflow Phase 2 (Route) for codegen intents.
For the 8-phase workflow see ai-native-workflow/SKILL.md. For worked examples and troubleshooting see this skill's references/.
Critical
These rules are unique to template usage. All other rules (selectors, waits, types, Zod strictness, response validation, tags, fixtures, JSDoc, no-XPath, no-hardcoded-strings, etc.) live in the CLAUDE.md Constitution and the leaf skills (api-testing, page-objects, selectors, test-standards, data-strategy, type-safety, fixtures, enums). Re-read the Constitution + the matching leaf skill's Critical block before generating from any template here.
- Resolve
{area}first. Every template contains{area}as a placeholder. Run the matchingls(ls pages/,ls tests/,ls fixtures/api/schemas/,ls test-data/factories/,ls test-data/static/,ls enums/) and substitute the real folder name before filling the template. Do not guess. - Templates are starters, not substitutes. Each template is a 10-15 line scaffold. The leaf skill listed for the category owns the deep rules — load it and follow it end-to-end. Never reimplement a leaf skill's rules inline in your prompt.
- Walk the verification checklist (below) after generating. It is the canonical post-codegen audit; the leaf skills point here for it.
Instructions
Phase 1: Identify the task category and resolve paths
Match the user's request to one row, then run the ls commands the row's templates need.
| Category | Template section | Specialized skill(s) | ls to run before filling |
|---|---|---|---|
| Page object / component | Page Object Tasks | page-objects, selectors, playwright-cli |
ls pages/ |
| Functional / E2E test | Test Tasks | test-standards, data-strategy |
ls tests/, ls test-data/factories/ |
| API test | Test Tasks → Add API Test | api-testing, test-standards |
ls tests/, ls fixtures/api/schemas/, ls enums/ |
| Zod response schema | API Schema Tasks | api-testing, type-safety |
ls fixtures/api/schemas/ |
| Data factory | Data Factory Tasks | data-strategy, type-safety |
ls test-data/factories/ |
| Static test data | Data Factory Tasks → Static Test Data | data-strategy, api-testing |
ls test-data/static/ |
| Fixture (POM / helper) | Fixture Tasks | fixtures, helpers |
(no path placeholder) |
| UI component | Component Tasks | page-objects, selectors |
(no path placeholder) |
What ships with it
8 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/examples.md 4.7 KB
- references/templates/api-schemas.md 2.8 KB
- references/templates/components.md 503 B
- references/templates/data.md 2.1 KB
- references/templates/fixtures.md 1.7 KB
- references/templates/page-objects.md 2.5 KB
- references/templates/tests.md 4.1 KB
- references/troubleshooting.md 4.0 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 · 111 lines · 177 tokens per session scan A 2e0e7bc0030c
common-tasks is a skill published in the GitHub repository idavidov13/agentic-playwright (159 stars, last pushed today), licensed MIT. It adds 177 tokens to every session and 2,319 once invoked, about $0.0009 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-08-30.
Other skills, from other repositories
vindicate
Use when the user wants to write, add, fix, stabilize (flaky), refactor, run, or audit Playwright browser tests, draft requirements/stories from a recording (no tests), find test-coverage gaps, scaffold a Playwright project, or set up Playwright CI. Vindicate's guided workflow for grounded, conformant Playwright test…
editorial-illustrations
Generate meaning-carrying editorial data-illustrations in the monotykamary / Linear aesthetic (near-black grayscale, Inter display + mono labels, hairline framed figures) with a single coral accent. This is a GENERATIVE GUIDE, not a template gallery: it teaches the "claim -> geometry" method so any session can invent…
daily-journal
A passive daily work journal that Claude keeps FOR you so you never have to write it yourself. Append short entries after meaningful work (what was done, what you focused on, artifacts touched) to 01-daily/journal/YYYY-MM-DD.md. Run a guided reflection at night or in the morning. Use when you run /daily-journal, say…
product-ui-taste
Anti-slop skill for PRODUCT UI - dashboards, data tables, forms, multi-step flows, settings, list/detail, app shells. The agent reads the surface, budgets the frame first, and ships dense interfaces that are correct at every edge case (overflow, long labels, empty/error/loading states, i18n expansion, keyboard/a11y).…
review-cockpit
Produce and continuously maintain ONE living review document for a multi-item session — a cockpit header (Progress checklist, Working folder, Context) plus per-item review cards that you approve or request changes on directly in the doc or side panel. Use whenever a session has multiple deliverables you need to…
ultragoal
Run a large, multi-session goal (e.g. shipping a whole side product) through the full V-model closed loop, one phase at a time, with cross-session state and a final north-star acceptance gate. Ultragoals never downgrade the lane: every phase runs CP-1→CP-6 with adversarial verification. Opt-in: invoke with /ultragoal…