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 andresquirogadev/skillsense --skill playwrightgit clone --depth 1 https://github.com/andresquirogadev/skillsenseWrote 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/andresquirogadev/skillsense/playwright)<a href="https://agentmods.dev/skills/andresquirogadev/skillsense/playwright"><img src="https://agentmods.dev/badge/skills/andresquirogadev/skillsense/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/andresquirogadev/skillsense/playwright"><img src="https://agentmods.dev/badge/skills/andresquirogadev/skillsense/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.00000 | $0.00535 |
| Opus 5 | $0.00000 | $0.00267 |
| Sonnet 5 | $0.00000 | $0.00107 |
| Haiku 4.5 | $0.00000 | $0.00053 |
Grade A, and why
playwright 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 8d 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 — 49 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Playwright Skill
You are writing end-to-end tests with Playwright. Apply these conventions.
Test Structure
- Each test file covers a user-facing feature or flow, not a single component.
- Use
test.describefor grouping related flows. - Use
test.beforeEachto navigate to the starting URL rather than duplicatingpage.goto()in every test. - Use Page Object Model (POM) for complex flows — create classes in
tests/pages/that encapsulate selectors and actions.
Selectors
- Prefer user-visible locators in priority order:
getByRole('button', { name: 'Submit' })— semantic and accessiblegetByLabel('Email')— form inputsgetByTestId('submit-btn')— usedata-testidas a last resort for dynamic content
- Avoid CSS selectors and XPath — they couple tests to implementation details.
- Use
locator.filter({ hasText: '…' })to narrow a locator.
Assertions
- Use
expect(locator).toBeVisible(),toHaveText(),toHaveValue()— these auto-retry until the condition passes or timeout. - Avoid
waitForSelector—expect()assertions include built-in waiting. - Use
expect(page).toHaveURL('/dashboard')after navigation.
Network
- Mock API calls for unit-level e2e tests:
page.route('**/api/users', route => route.fulfill({ json: mockUsers })). - Use
page.waitForResponse('**/api/submit')to wait for network requests triggered by actions.
Performance & Reliability
- Run tests in parallel by default (Playwright's default); use
test.describe.serialonly for tests with hard ordering dependencies. - Always run tests against a local dev server; configure
webServerinplaywright.config.ts. - Use
test.slow()to extend the timeout for known slow tests instead of setting global timeouts high. - Capture screenshots on failure:
use: { screenshot: 'only-on-failure' }in config.
playwright.config.ts
export default defineConfig({
testDir: './tests',
fullyParallel: true,
use: { baseURL: 'http://localhost:3000', trace: 'on-first-retry' },
webServer: { command: 'npm run dev', url: 'http://localhost:3000', reuseExistingServer: !process.env.CI },
});
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.
- 8d ago First seen · 49 lines · 0 tokens per session scan A 60c9f36881a2
playwright is a skill published in the GitHub repository andresquirogadev/skillsense (2 stars, last pushed 5mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 535 tokens. 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-31.
Other skills, from other repositories
e2e
Generate and run Playwright E2E tests traced to spec.md acceptance criteria, with an optional accessibility audit. Use when saying "e2e tests" or "a11y audit".
ui-aqa-flow
Workflow for automated QA: integration and end-to-end UI test automation, page objects, etc.
qa-knowledge
To run QA engineering — requirements/gap analysis, scenario & spec design, test implementation, failure triage — over the QA knowledge base.
ralphctl-test-driven-development
Execute-phase skill — write the failing test before the code that makes it pass; for bug fixes, this is the reproduction test itself. Use for any logic change, bug fix, or behavioural modification; for the full root-cause triage pipeline around an unexpected failure, see ralphctl-debugging-and-error-recovery.
qamap-pr-qa
Local zero-LLM PR QA workflow. Use when an agent is preparing, updating, finalizing, or reviewing a pull request, asks what the PR should test, or needs commit-backed change intent, affected behavior, QA scenarios, evidence, validation commands, optional automation drafts, and manifest repair guidance.
tauri-pilot
Inspect, interact with, and test a running Tauri v2 app via CLI. Communicates over Unix socket using JSON-RPC 2.0. Use when testing UI, automating interactions, or debugging a Tauri app.