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 andrewsrigom/agent-skills --skill playwright-network-control-and-api-synchronizationgit clone --depth 1 https://github.com/andrewsrigom/agent-skillsWrote 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/andrewsrigom/agent-skills/playwright-network-control-and-api-synchronization)<a href="https://agentmods.dev/skills/andrewsrigom/agent-skills/playwright-network-control-and-api-synchronization"><img src="https://agentmods.dev/badge/skills/andrewsrigom/agent-skills/playwright-network-control-and-api-synchronization/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/andrewsrigom/agent-skills/playwright-network-control-and-api-synchronization"><img src="https://agentmods.dev/badge/skills/andrewsrigom/agent-skills/playwright-network-control-and-api-synchronization.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.00057 | $0.00755 |
| Opus 5 | $0.00028 | $0.00378 |
| Sonnet 5 | $0.00011 | $0.00151 |
| Haiku 4.5 | $0.00006 | $0.00076 |
Grade A, and why
playwright-network-control-and-api-synchronization 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 9d 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 — 88 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Playwright Network Control And API Synchronization
Use this skill when the test problem is really about backend timing, request control, or mocking boundaries.
Scope
- waiting on meaningful network activity
- route interception and mocking
- API request contexts
- backend synchronization
- deciding what should be mocked vs exercised end to end
Routing cues
page.route, request interception, API mocking,waitForResponse,APIRequestContext, backend synchronization, flaky loading due to network timing, or when to mock -> use this skill- locator or assertion fragility -> use
playwright-locators-assertions-and-user-visible-contracts - auth state and role reuse -> use
playwright-auth-projects-and-isolation - traces, flaky failure analysis, or codegen cleanup -> use
playwright-debugging-traces-and-flake-reduction
Default path
- Prefer real backend flows for the core happy path when they are stable and meaningful to the product.
- Synchronize on visible outcomes first, and on targeted network events second when the UI alone is not enough.
- Mock only the dependencies that make the test too slow, too flaky, or too hard to control.
- Keep mocks narrow and scenario-specific.
- Use API request contexts for setup and teardown when that keeps UI tests focused on the right surface.
When to deviate
- Mock more aggressively only when third-party dependencies or rare failure branches are the real subject.
- Wait on network events directly only when the visible UI signal is too indirect or ambiguous.
- Use fully mocked flows for deterministic edge-case coverage that would be impractical end to end.
Guardrails
- do not over-mock the product's own critical behavior
- network waits should correspond to a meaningful contract
- setup via API is fine when it removes irrelevant UI churn
- mocks should remain readable and local to the scenario they support
Avoid
- mocking the very backend contract the test is supposed to validate
- waiting on every request instead of the one that matters
- leaving broad route interception in place across unrelated tests
- using network control as a substitute for fixing broken locator or assertion strategy
What ships with it
1 file 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.
- 9d ago First seen · 88 lines · 57 tokens per session scan A 30f6d6e14d3b
playwright-network-control-and-api-synchronization is a skill published in the GitHub repository andrewsrigom/agent-skills (2 stars, last pushed 5mo ago), licensed MIT. It adds 57 tokens to every session and 755 once invoked, about $0.0003 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-31.
Other skills, from other repositories
browse
Drive a real browser through Aside: open a page, read it, click through a flow, take screenshots, check console errors. (gstack).
playwright-cli
A command-line tool for controlling Chromium, Firefox, and WebKit browsers, including navigation, page interaction, screenshots, PDFs, and recorded actions.
webapp-testing
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.
create-verification-skill
Create a repo-local verification skill and exhaustive feature map for driving a real app through its UI, CLI, or API. Use for "create a verification skill", "make a verify skill for this repo", or "document how agents can verify this app".
browser-qa
A browser-based quality check for deployed web pages and user flows. It uses browser automation to test rendering, navigation, forms, interactions, responsive behaviour, and accessibility-related issues.
test-electron-app
Drive the real running PostHog Electron app (live tRPC, workspace-server, real data) over CDP with agent-browser. Connect to the running app on port 9222, test desktop changes against a local Django stack, snapshot the accessibility tree, inspect network requests, and screenshot only when explicitly asked. Use when…