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/chankov/agent-fleet/bowsernpx skills add chankov/agent-fleet --skill bowsergit clone --depth 1 https://github.com/chankov/agent-fleetWrote 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/chankov/agent-fleet/bowser)<a href="https://agentmods.dev/skills/chankov/agent-fleet/bowser"><img src="https://agentmods.dev/badge/skills/chankov/agent-fleet/bowser.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.00059 | $0.01563 |
| Opus 5 | $0.00030 | $0.00781 |
| Sonnet 5 | $0.00012 | $0.00313 |
| Haiku 4.5 | $0.00006 | $0.00156 |
Grade A, and why
bowser 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 5d 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 — 146 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Playwright Bowser
Purpose
Automate browsers using playwright-cli — a token-efficient CLI for Playwright. Runs headless by default, supports parallel sessions via named sessions (-s=), and doesn't load tool schemas into context.
Requirements
This skill drives the external Playwright Agent CLI (playwright-cli). It is not bundled with agent-fleet — install it once before using this skill (the guided setup checks for it when bowser is selected).
- Node.js 20+
playwright-cli— install globally:
npm install -g @playwright/cli@latest
playwright-cli --help # verify it responds
Or run ad-hoc without a global install via npx playwright-cli <command>.
Browsers are downloaded automatically on first use; to pre-install explicitly:
playwright-cli install-browser # default (chromium)
playwright-cli install-browser firefox # a specific browser
playwright-cli install-browser --with-deps # include system dependencies
Full install docs: https://playwright.dev/agent-cli/installation
When to use this vs Chrome DevTools MCP
This skill (playwright-cli) and the chrome-devtools-mcp pi extension are complementary, not redundant — they differ by tool model, not just headless-vs-headful (both can do either):
bowser/playwright-cli(this skill) — CLI-driven, headless-first, parallel named sessions, token-efficient (no tool schemas in context). It needs only Bash, so it works as a dispatched subagent under--no-extensions. Use it for automated, parallel, or background runtime-UI evidence and scraping.web-debugger/chrome-devtools-mcp— livechrome_devtools__*tools (DOM/console/network/performance traces) for interactive headful debugging with a human in the loop. Those tools come from an always-on extension, so they are reachable in the main session or a coms peer, not a--no-extensionssubagent. Use it to understand a failure in a running dev app.
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.
- 5d ago First seen · 146 lines · 59 tokens per session scan A 753bd7cfe440
bowser is a skill published in the GitHub repository chankov/agent-fleet (13 stars, last pushed today), licensed MIT. It adds 59 tokens to every session and 1,563 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
v8-jit
V8 JIT optimization patterns for writing high-performance JavaScript in Next.js server internals. Use when writing or reviewing hot-path code in app-render, stream-utils, routing, caching, or any per-request code path. Covers hidden classes / shapes, monomorphic call sites, inline caches, megamorphic deopt, closure…
use-agent-browser-for-airi
Test AIRI display-model imports with agent-browser across stage-tamagotchi Electron, stage-web, and stage-pocket mobile web layouts. Use when uploading and verifying contributor-supplied Live2D ZIP, VRM, or MMD ZIP/PMX/PMD files through AIRI's model selector, including onboarding bypass, format-specific import…
opencli-sitemap-author
Use when creating or maintaining OpenCLI site sitemaps: agent-facing navigation, page-state, action, workflow, API-reference, pitfall, and fallback knowledge for a website. Use after browser exploration discovers durable site context, when a sitemap is stale, or when promoting local site knowledge into the repo.
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…
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.
interactive-login
How to complete browser/interactive logins (aws / gh / glab / gcloud). The platform backgrounds the login poller so it survives the human's browser round-trip — and when that does NOT work.