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 xAmirHamza77/ReverseOps-Skill --skill browser-automationgit clone --depth 1 https://github.com/xAmirHamza77/ReverseOps-SkillWrote 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/xamirhamza77/reverseops-skill/browser-automation)<a href="https://agentmods.dev/skills/xamirhamza77/reverseops-skill/browser-automation"><img src="https://agentmods.dev/badge/skills/xamirhamza77/reverseops-skill/browser-automation.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.1 | $0.00126 | $0.01935 |
| Opus 5 | $0.00063 | $0.00967 |
| Sonnet 5 | $0.00025 | $0.00387 |
| Haiku 4.5 | $0.00013 | $0.00194 |
Grade A, and why
browser-automation 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 6d 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 — 243 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Automation Operations (Desktop & Browser Automation)
ACTION REQUIRED (execute immediately after reading)
NOW: Confirm whether the current task falls within the scope of this skillNOW: Read../tool-index.mdto verify tool availability and actual pathsNEXT: When a tool is missing, invoke the bootstrap; do not guess pathsACT: Go to the first step of the "Workflows" section and execute it; do not stop at the confirmation stage
Scope
Use this skill when the task falls into one of the following scenarios:
Browser scenarios (Playwright / agent-browser)
- Open a web page and operate page elements (click, fill forms, submit)
- Scrape page content or take screenshots
- Automate login flows
- Interact with web pages during penetration testing (submit payloads, trigger XSS)
- Automated handling of captcha pages
- Batch form submission
Desktop application scenarios (OpenReverse)
- Operate Windows desktop applications (IDA Pro, x64dbg, Wireshark, etc.)
- Vision-driven interaction (CUA mode)
- Structured UI operations (UIA mode)
- Network traffic observation of desktop applications (built-in mitmproxy)
- Automating the GUI of reversing tools
- Black-box testing of desktop software
Division of labor with other tools
| Scenario | What to use |
|---|---|
| Operate web pages (inside a browser) | Playwright / agent-browser |
| Operate desktop applications (Windows GUI) | OpenReverse |
| Packet capture analysis, HTTP request capture | anything-analyzer or OpenReverse network lane |
| JS breakpoints, hooks, CDP debugging | jshookmcp |
| Locate signing algorithms, reproduce with environment emulation | js-reverse |
Simple rule of thumb:
- Target is a web page → Playwright
- Target is a Windows desktop application → OpenReverse
- Both are needed → use them together
Part 1: Browser automation (Playwright / agent-browser)
Core workflow
# 1. Open the page
agent-browser open <url>
# 2. Get interactive elements (returns @e1, @e2... references)
agent-browser snapshot -i
# 3. Operate elements using the references
agent-browser click @e1
agent-browser fill @e2 "text"
# 4. Close when done
agent-browser close
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.
- 6d ago First seen · 243 lines · 126 tokens per session scan A 5af0da4dea47
browser-automation is a skill published in the GitHub repository xAmirHamza77/ReverseOps-Skill (4 stars, last pushed 1mo ago), licensed MIT. It adds 126 tokens to every session and 1,935 once invoked, about $0.0006 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
scraperapi-n8n
Generate n8n workflows that use the official ScraperAPI community node (n8n-nodes-scraperapi-official). Use this skill whenever the user wants to build, design, automate, or scaffold an n8n workflow that scrapes the web through ScraperAPI — even when they don't say "skill" or "ScraperAPI node" by name. Triggers…
scraperapi-cli
Product-usage reference for the official ScraperAPI command-line tool (sapi, distributed as scraperapi-cli). Use this skill whenever the user wants to scrape, run async jobs, fetch structured data, manage crawls, check account credits, or drive DataPipeline projects from a terminal or shell script — anywhere a…
scraperapi-scraper-builder
Build and implement web scrapers using ScraperAPI. Use this skill whenever the user asks to build, write, create, or implement a scraper, or wants runnable code that extracts data from a website. Trigger on: "build me a scraper for [website]", "write a scraper that fetches product pages from [ecommerce site]", "I need…
scraperapi-zapier
Guide users to build Zaps that use the official ScraperAPI Zapier integration. Use this skill whenever the user wants to add web scraping, SERP data, or e-commerce data to a Zapier workflow through ScraperAPI — even when they don't say "skill" or name the integration. Triggers include: "build a Zap that scrapes Amazon…
scraperapi-datapipeline
Product-usage reference for ScraperAPI's DataPipeline — managed, scheduled scraping projects that run automatically and deliver results to a webhook or dashboard download. Consult when the user needs recurring scraping, has a large list of URLs/ASINs/queries to process, or wants to avoid building and maintaining their…
scraperapi-research-agent
Autonomous web research agent — takes a research question, uses ScraperAPI to discover and scrape relevant sources, uploads content as file artifacts to the Anthropic Files API, then feeds everything to Claude for synthesis into a cited research report. All in one flow. Use when user asks: "research X for me and give…