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 nobrainer-tech/nobrainer-tech-skills --skill nobrainer-browsergit clone --depth 1 https://github.com/nobrainer-tech/nobrainer-tech-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/nobrainer-tech/nobrainer-tech-skills/nobrainer-browser)<a href="https://agentmods.dev/skills/nobrainer-tech/nobrainer-tech-skills/nobrainer-browser"><img src="https://agentmods.dev/badge/skills/nobrainer-tech/nobrainer-tech-skills/nobrainer-browser/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/nobrainer-tech/nobrainer-tech-skills/nobrainer-browser"><img src="https://agentmods.dev/badge/skills/nobrainer-tech/nobrainer-tech-skills/nobrainer-browser.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.00094 | $0.01549 |
| Opus 5 | $0.00047 | $0.00775 |
| Sonnet 5 | $0.00019 | $0.00310 |
| Haiku 4.5 | $0.00009 | $0.00155 |
Grade A, and why
nobrainer-browser 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 7d 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 — 161 lines — stays where its author put it; the contents beside it link to each section on GitHub.
NoBrainer Browser
Use one Playwright-first browser path. The agent-focused @playwright/cli
drives and inspects pages; the repository's Playwright test CLI records and
opens traces. Do not add a second browser framework merely because one exists.
Route the task
| Need | Default |
|---|---|
| Inspect a rendered page, follow navigation, read dynamic content | playwright-cli |
| Reuse an approved logged-in Chrome/Edge session | playwright-cli attach over CDP |
| Run or debug repository tests | the repository's npx playwright test |
| Record or inspect failure evidence | Playwright trace + show-trace |
| Plain static content already available without a browser | use the cheaper read path |
Do not install MCP when the CLI covers the task. Do not install a browser plugin as the default path. Reuse an already configured MCP only when the current harness cannot run the CLI and the MCP has fresh capability readback.
Capability and install gate
First inspect the repository and machine:
command -v playwright-cli && playwright-cli --version
test -f package.json && npm exec playwright -- --version
npm view @playwright/cli dist-tags.latest --json
For interactive agent work, use the current npm channel only to discover a version, then pin that exact version for execution and record the readback:
PLAYWRIGHT_CLI_VERSION="$(npm view @playwright/cli version)"
test -n "$PLAYWRIGHT_CLI_VERSION"
npm install -g "@playwright/cli@$PLAYWRIGHT_CLI_VERSION"
playwright-cli --version
playwright-cli --help
playwright-cli --help attach
Package installation is a machine write. Perform it only when setup is within scope, and do not claim success until the binary readback passes. For a test repository, prefer its lockfile and package scripts over changing dependencies.
The CLI also offers playwright-cli install --skills. Do not run it by default
while nobrainer-browser owns browser routing: that would add another skill
owner with overlapping triggers. Read the live CLI help instead. If the owner
chooses the upstream Playwright skills, reconcile to one browser-skill owner
rather than keeping both active.
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.
- 7d ago Changed · +13 lines · +13 tokens per session 3e78970b25d0
- 8d ago Changed · +2 lines · +6 tokens per session 5339b526a5ad
- 12d ago First seen · 146 lines · 75 tokens per session scan A a4c1d684979c
nobrainer-browser is a skill published in the GitHub repository nobrainer-tech/nobrainer-tech-skills (5 stars, last pushed 7d ago), licensed MIT. It adds 94 tokens to every session and 1,549 once invoked, about $0.0005 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
playwright-tabbed-orchestration
Parent Agent uses playwright-tabbed to allocate browser tabs and partition tasks, then spawns child agents in parallel — each operating on its assigned tabid — for browser acceptance testing or automation, with a final aggregated summary. Suitable for multi-page validation, parallel module checks, and…
e2e-testing-patterns
Master end-to-end testing with Playwright and Cypress to build reliable test suites that catch bugs, improve confidence, and enable fast deployment. Use when implementing E2E tests, debugging flaky tests, or establishing testing standards.
browser-testing-with-devtools
Tests in real browsers via Chrome DevTools MCP. Use when building or debugging anything that runs in a browser. Use when you need to inspect the DOM, capture console errors, analyze network requests, profile performance, or verify visual output with real runtime data. Requires the chrome-devtools MCP server to be…
agent-browser
Automates browser interactions for web testing, form filling, screenshots, and data extraction. Use when the user needs to navigate websites, interact with web pages, fill forms, take screenshots, test web applications, or extract information from web pages.
qa/e2e-playwright
A method for writing Playwright end-to-end tests, which automate a browser to verify complete user journeys. It covers setup, reusable page objects, login reuse, API mocking, visual checks, multiple browsers and screen sizes, CI, and debugging.
Console Error Hunter
Systematically detect, capture, and categorize browser console errors, warnings, and unhandled exceptions during automated test execution.