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 Mallikarjun-Roddannavar/playwright-agentic-automation --skill pw-api-pomgit clone --depth 1 https://github.com/Mallikarjun-Roddannavar/playwright-agentic-automationWrote 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/mallikarjun-roddannavar/playwright-agentic-automation/pw-api-pom)<a href="https://agentmods.dev/skills/mallikarjun-roddannavar/playwright-agentic-automation/pw-api-pom"><img src="https://agentmods.dev/badge/skills/mallikarjun-roddannavar/playwright-agentic-automation/pw-api-pom/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/mallikarjun-roddannavar/playwright-agentic-automation/pw-api-pom"><img src="https://agentmods.dev/badge/skills/mallikarjun-roddannavar/playwright-agentic-automation/pw-api-pom.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.00064 | $0.00812 |
| Opus 5.5 | $0.00026 | $0.00325 |
| Sonnet 5.5 | $0.00013 | $0.00162 |
| Haiku 4.5 | $0.00006 | $0.00081 |
Grade A, and why
pw-api-pom 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 1mo 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 — 90 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PW API POM
Maintain the API automation layer in a way that keeps tests explicit and services reusable.
Use This Skill When
- Adding a new API scenario under
api/specs. - Updating request/response handling in
api/services. - Cleaning up raw API tests so they match the service/spec boundary conventions.
- Adjusting authenticated request-context behavior in
utils/fixtures/TestFixtures.ts. - Changing auth token flow or role bootstrap behavior.
Follow These Rules
- Keep API services under
api/services. - Keep API specs under
api/specs. - Keep services assertion-free.
- Return raw
APIResponseobjects from services. - Put assertions in specs, including negative scenarios.
- Use aliases such as
@api/*,@utils/*, and@config/*.
Inspect First
- Identify the affected service, spec, fixture, and any auth/bootstrap file before editing.
- Reuse an existing service method before adding a new one.
- If the task changes credentials or token flow, inspect auth setup and fixture usage together.
- If a route is involved, inspect
BaseApiService.routesfirst.
Decide What To Edit
- Edit a service when request construction, route usage, or response parsing changes.
- Edit a spec when the expected status, payload, or role-based behavior changes.
- Edit a fixture when authenticated request-context creation changes.
- Keep assertion logic out of services even when handling failure paths.
New API Scenario Flow
- Inspect a similar spec and any related service methods.
- Reuse an existing authenticated fixture if one already matches the role.
- Add or update the service method only if the request shape is new.
- Keep all assertions in the spec body.
- Register cleanup through the shared
cleanupfixture as soon as the test has the created resource id. - Validate with the smallest relevant command set.
Cleanup Raw API Tests
- Treat direct request calls in specs as cleanup candidates when a service already owns that behavior.
- Move request construction into services.
- Keep assertions and negative-path expectations in specs.
- Reuse route constants and authenticated fixtures before adding new helpers.
- Keep the service reusable for both positive and negative scenarios.
What ships with it
2 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.
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.
- 1mo ago First seen · 90 lines · 64 tokens per session scan A 25d20938b4c7
pw-api-pom is a skill published in the GitHub repository Mallikarjun-Roddannavar/playwright-agentic-automation (13 stars, last pushed 20d ago), licensed MIT. It adds 64 tokens to every session and 812 once invoked, about $0.0003 per session on Opus 5.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-31.
Other skills, from other repositories
emulate-seed
Generate emulate seed configs for stateful API emulation. Wraps Vercel's emulate tool for GitHub, Vercel, Google OAuth, Slack, Apple Auth, Microsoft Entra, AWS, Okta, Clerk, Resend, Stripe, and MongoDB Atlas APIs — full state machines, not mocks. Use when setting up test environments, CI pipelines, integration tests…
browser-qa
Testing web apps through a real browser: reconnaissance before acting, selector discovery, state capture, console errors and screenshot evidence. Use on a web surface end to end, or to reproduce a front-end bug.
backend-manual-testing
Use when the task touches a backend API, database or worker - booting it from the task branch, driving real requests and verifying side effects (DB rows, outbound calls, logs) as evidence.
Skill: Verify server/API changes (example for Verify skill)
Example workflow for verifying a server/API change, as part of the Verify skill.
verify
How to run and drive this app to verify UI/server changes at runtime.
sidekick-audit
Deterministic UI quality audit of a web page or a whole product — WCAG 2.2 A/AA accessibility (axe-core), Core Web Vitals (LCP/CLS), browser health (console errors, failed requests, mixed content) and tap-target size — reported dimensions-first, with confirmed-vs-uncertain findings clustered into root-cause families…