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/5uck1ess/devkit/browsernpx skills add 5uck1ess/devkit --skill browsergit clone --depth 1 https://github.com/5uck1ess/devkitWhat 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.00058 | $0.01624 |
| Opus 5 | $0.00029 | $0.00812 |
| Sonnet 5 | $0.00012 | $0.00325 |
| Haiku 4.5 | $0.00006 | $0.00162 |
Grade A, and why
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 yesterday.
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 — 162 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Browser Automation
Drive a real browser via Playwright to interact with pages — click, fill forms, extract data from SPAs, run multi-step flows, or record user interactions.
Use this skill for anything beyond simple article scraping: JS-heavy data extraction, form filling, multi-step auth flows, codegen recording, or E2E testing. For static article→markdown use scrape; for pure image capture use screenshot.
Step 1: Verify Playwright
Run npx playwright --version. If it fails, stop and tell the user: Playwright required — install with: npx playwright install chromium. Do not attempt workarounds.
Step 2: Parse the Request
- Target URL(s) — starting page (validate per Rules before launching)
- Actions — navigate, click, fill, extract, wait
- Data — what fields, what format (JSON usually)
- Auth — are credentials needed? Read from env, never hardcode
- Repeatability — one-off throwaway, or save script for reuse?
If the request is vague ("scrape this site"), clarify which fields, whether login is needed, and whether it'll be re-run.
Step 3: Choose the Right Mode
Mode A — Codegen (recording)
When the user wants to figure out selectors or hand off a repeatable flow:
npx playwright codegen {url}
Opens a browser. User interacts. Playwright prints the equivalent script. Best for:
- Complex pages where selectors aren't obvious
- Building reusable flows
- Teaching users how Playwright works
Mode B — Inline script (one-off)
Write the script to a file that reads args from process.argv, then pass values via shell variables:
cat > /tmp/devkit-browser-flow.mjs <<'EOF'
import { chromium } from 'playwright';
const url = process.argv[2];
if (!url) { console.error('usage: node devkit-browser-flow.mjs <url>'); process.exit(2); }
const browser = await chromium.launch();
let exitCode = 0;
try {
const page = await browser.newPage();
await page.goto(url, { waitUntil: 'networkidle', timeout: 30000 });
// Example: extract items from a JS-rendered list
const data = await page.evaluate(() =>
Array.from(document.querySelectorAll('.item')).map(el => ({
title: el.querySelector('h3')?.textContent?.trim(),
link: el.querySelector('a')?.href,
}))
);
console.log(JSON.stringify(data, null, 2));
} catch (err) {
console.error('flow failed:', err.message);
exitCode = 1;
} finally {
try { await browser.close(); } catch (e) { /* suppress close errors so the real error propagates */ }
}
process.exit(exitCode);
EOF
URL=https://example.com node /tmp/devkit-browser-flow.mjs "$URL"
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.
- yesterday First seen · 162 lines · 58 tokens per session scan A 44e3f087a174
browser is a skill published in the GitHub repository 5uck1ess/devkit (5 stars, last pushed 13d ago), licensed MIT. It adds 58 tokens to every session and 1,624 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
mootdx
Mootdx A-share market data via TCP-direct 通达信 servers. Free, no API key, no IP rate limits. Use as the stable A-share OHLCV fallback when akshare's East Money scrape is throttled.
pr-screenshots
Capture Playwright screenshots and embed them in GitHub PR descriptions.
Video Editor (FFmpeg)
AI-powered Video Editor with trimming, merging, effects, overlays, and export.
Codex
Mission control: create tasks, assign to an agent/team, wait for human approval, worker runs in the background, accept results.
File Manager
Manage files and folders on the computer.
browser_scripts
Visual browser automation script editor & manager for TubeCLI.