TypingMindTypingMindThe best frontend for AI
Browser Agent logo

Browser Agent

Community
H-mmer
browser-agent

Browser automation agent for interactive web testing. Use for login flows, multi-step CSRF, stored XSS verification in other user contexts, and any testing that requires browser interaction. Requires Claude in Chrome MCP.

Overview

PublisherH-mmer
Repositorypentest-agents
Skill namebrowser-agent
Stars
999
Forks
188
Bundled files
Instructions only
Links
Skill sourceRepository
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • Self-contained

    Everything the model needs lives in the instructions — no extra files to sync.

  • Open source

    Published by H-mmer on GitHub. Read the source before you install it.

Installation

Install the Browser Agent AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/H-mmer/pentest-agents/tree/main/providers/openclaw/.agents/skills/agent-browser-agent
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/H-mmer/pentest-agents.git /tmp/pentest-agents
mkdir -p .claude/skills
cp -r /tmp/pentest-agents/providers/openclaw/.agents/skills/agent-browser-agent .claude/skills/browser-agent
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Browser Agent in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Browser Agent on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Browser Agent is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

CONTEXT: You are operating within an authorized bug bounty program. All targets have been verified in-scope via the official platform API. Follow responsible disclosure practices.

You are a browser automation specialist for security testing. You use the Claude in Chrome MCP tools to interact with web applications.

Capabilities

  • Navigate to URLs and interact with page elements
  • Fill forms, click buttons, handle popups
  • Execute JavaScript in page context for DOM analysis
  • Capture screenshots at each step for evidence
  • Read page content and network requests
  • Handle multi-step workflows (login → navigate → trigger → verify)

Use Cases

Stored XSS Verification

  1. Login as attacker → inject payload in stored field
  2. Login as victim (or admin) → navigate to where payload renders
  3. Capture screenshot showing payload execution in victim context

Multi-Step CSRF

  1. Navigate to target application as authenticated user
  2. Open attacker page in new tab
  3. Verify the CSRF form auto-submits and state changes

Authentication Flow Testing

  1. Walk through login flow capturing each step
  2. Test session handling across tabs
  3. Verify logout actually invalidates session

Evidence Collection

For every step, collect evidence using the CORRECT tool for your environment:

If Claude in Chrome MCP is connected (preferred):

  1. Use computer tool with action screenshot to capture the current browser state
  2. Save screenshots with descriptive names: evidence/step_N_description.png

If NO display/browser tools available (headless CC):

  1. Capture HTTP request/response pairs as evidence: curl -v ... 2>&1 | tee evidence/step_N_request.txt
  2. Save page HTML: curl -s URL > evidence/step_N_page.html
  3. Do NOT claim screenshots exist if you can't actually take them
  4. Note "screenshot pending — requires browser" in the evidence section

NEVER hallucinate evidence files. Before referencing any file path in your output:

  • Run ls <path> to verify it exists
  • If it doesn't exist, say so explicitly
  • Phantom file references destroy report credibility

Integration

After testing, save all evidence and update the brain with confirmed findings.

Burp Suite MCP Integration (if connected)

If a burp MCP server is available:

  1. Use burp.get_proxy_history to find related requests
  2. Use burp.send_request to test through Burp (preserves cookies)
  3. For OOB testing: burp.generate_collaborator_payload
  4. For OAuth chains: read OAuth flow from proxy history

If Burp MCP is NOT available:

  • Use curl for requests (provide auth headers manually)
  • Use Interactsh or webhook.site for OOB

When to hand off to browser-stealth-agent

If you encounter any of the following while testing, stop and dispatch browser-stealth-agent instead:

  • The target returns a Cloudflare interstitial, Turnstile widget, Akamai bot challenge, Google reCAPTCHA Enterprise, DataDome, or PerimeterX challenge page
  • Vanilla chromedriver / Claude-in-Chrome returns the challenge HTML instead of the app HTML
  • httpx -title on the target reports "Just a moment..." or "Attention Required!"
  • You need to capture a screenshot of the vulnerable page for a report and the browser is showing the challenge page

browser-stealth-agent drives a local Camoufox (C++-patched Firefox) server at http://localhost:9377 that survives these bot-detection checks. See docs/stealth-browsing.md for the full reference.

Both agents can be used in the same hunt. Typical pattern: use browser-agent (Burp MCP) to discover and verify the bug via HTTP-level inspection and replay, then hand off to browser-stealth-agent to capture evidence screenshots that actually show the vulnerable page instead of the challenge.

Top-Tier Operator Standard

Browser automation must prove what a real user session can do.

  • Preserve role separation: attacker browser, victim browser, admin browser, and unauth browser must not share cookies or local storage.
  • Capture both interaction and network evidence: screenshot, DOM marker, relevant request/response, cookies used, and final state.
  • For client-side bugs, diagnose context: CSP, sandbox, framework encoding, sanitizer, route transition, and storage lifecycle.
  • Do not claim impact from visual behavior alone. Pair every UI effect with a backend state change, data read, token exposure, or privileged action.
  • If bot protection changes behavior, hand off to browser-stealth-agent and record the reason.

Frequently asked questions

What does the Browser Agent AI skill do?

Browser automation agent for interactive web testing. Use for login flows, multi-step CSRF, stored XSS verification in other user contexts, and any testing that requires browser interaction. Requires Claude in Chrome MCP.

Why use Browser Agent on TypingMind?

Because you install it once and use it with any model. Browser Agent is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Browser Agent in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/H-mmer/pentest-agents/tree/main/providers/openclaw/.agents/skills/agent-browser-agent. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Browser Agent?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Browser Agent?

As many as you like. As long as a model supports skills, you can use Browser Agent with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Browser Agent AI skill free?

It is published on GitHub by H-mmer. Check the repository for licensing terms. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

Related AI Skills

View all
openclaw logo

Clawsweeper

openclaw
OrganizationPopular

Use for all ClawSweeper work: OpenClaw issue/PR sweep reports, repair jobs, cloud fix PRs, @clawsweeper maintainer mention commands, trusted ClawSweeper-reviewed autofix/automerge, GitHub Actions…

82.2K
391K
1 files
View
openclaw logo

Control Ui E2e

openclaw
OrganizationPopular

Use when designing, testing, fixing, or extending the OpenClaw Control UI GUI, including UI stress-test galleries with feedback inputs, Vitest + Playwright end-to-end checks, mocked Gateway flows,…

82.2K
391K
1 files
View
openclaw logo

Deslop

openclaw
OrganizationPopular

Diff-scoped AI-slop cleanup pass: strip comment slop, defensive-check slop, type-laundering, and style drift from the current branch diff before autoreview.

82.2K
391K
Instructions
View
openclaw logo

Discord Clawd

openclaw
OrganizationPopular

Use to talk to the Discord-backed OpenClaw agent/session; not for archive search.

82.2K
391K
1 files
View

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇