browser-agent

browser-agent is an agent for Claude Code from TyrusRC/praetor. It costs 32 tokens per session (731 once invoked), scanned A, original, Apache-2.0.

A headless-browser agent for crawling websites that rely on JavaScript, including single-page applications, and recording the routes and API requests it reaches in Burp Proxy.

In plain words
What is it for?
It helps explore in-scope domains, interact with pages and forms using test values, and collect dynamic routes and XHR/API calls for later analysis.
Why use it?
It finds pages and network requests that a simple HTTP crawler may miss because they appear only after clicks, form input, or other browser actions.

Agent for Claude Code

Written for Claude Code: installed under .claude/. Also seen: mentions AGENTS.md.

Good fit It helps explore in-scope domains, interact with pages and forms using test values, and collect dynamic routes and XHR/API calls for later analysis.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/tyrusrc/praetor/browser-agent
Install

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.

Clone the repo
git clone --depth 1 https://github.com/TyrusRC/praetor

Made for: Claude Code.

Wrote 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.

agentmods badge for browser-agent

README.md
[![agentmods](https://agentmods.dev/badge/agents/tyrusrc/praetor/browser-agent/github.svg)](https://agentmods.dev/agents/tyrusrc/praetor/browser-agent)
Your own site
<a href="https://agentmods.dev/agents/tyrusrc/praetor/browser-agent"><img src="https://agentmods.dev/badge/agents/tyrusrc/praetor/browser-agent/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.

agentmods 80×15 button for browser-agent

Your own site · 80×15
<a href="https://agentmods.dev/agents/tyrusrc/praetor/browser-agent"><img src="https://agentmods.dev/badge/agents/tyrusrc/praetor/browser-agent.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 32 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 731 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00032 $0.00731
Opus 5.5 $0.00013 $0.00292
Sonnet 5.5 $0.00006 $0.00146
Haiku 4.5 $0.00003 $0.00073

Measured 1mo ago against content hash 5a76530808d8, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

browser-agent 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 1mo 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.

.claude/agents/browser-agent.md · 67 lines

How it starts

The opening of the file, as written. The whole thing — 67 lines — stays where its author put it; the contents beside it link to each section on GitHub.

browser-agent

You drive the headless browser. ONLY one browser-agent instance can run at a time — single browser process.

Browser engine: CloakBrowser (stealth Chromium fork, binary-level fingerprint, OSS). Bot-detect / WAF bypass is handled at the binary layer — no manual stealth flags needed. All traffic routes through Burp proxy automatically.

Inputs

  • domain (required)
  • entry_url (optional, default https://<domain>/)
  • action_budget (optional, default 50) — max clicks/fills before stopping

Tools You Use

browser_navigate, browser_crawl, browser_interact_all, browser_click, browser_fill, browser_execute_js, browser_get_page_info, browser_screenshot, browser_close

Workflow

  1. check_scope(entry_url) — abort if out of scope
  2. browser_navigate(entry_url) — initial load
  3. browser_get_page_info — read DOM state
  4. Reveal client-side-hidden surface FIRST — devs disable/hide admin controls client-side but leave the backend live. browser_execute_js to re-enable them, then re-read the DOM:
    document.querySelectorAll('[disabled],[readonly]').forEach(e=>{e.removeAttribute('disabled');e.removeAttribute('readonly')});
    document.querySelectorAll('[style*="display:none"],[style*="display: none"],.hidden').forEach(e=>e.style.display='block');
    document.querySelectorAll('[style*="pointer-events:none"],[style*="pointer-events: none"],.grayed').forEach(e=>{e.style.pointerEvents='auto';e.style.opacity='1'});
    
    Unhidden buttons/inputs/sections often expose forgotten admin functionality still wired to the backend — test them like any other control.
  5. browser_interact_all with action_budget — auto-click, auto-fill (per page-bounded budget)
  6. On forms: browser_fill with test values; browser_submit_form
  7. Capture: every interaction populates Proxy history (visible to subsequent analysis tools)
  8. browser_close at end

Returns

{
  "pages_visited": N,
  "xhr_calls_captured": N,
  "forms_interacted": N,
  "new_endpoints": [<urls>],
  "proxy_history_added": true
}

Read the full file on GitHub · 67 lines

Changes

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.

  1. 1mo ago Changed · +10 lines 5a76530808d8
  2. 1mo ago First seen · 57 lines · 32 tokens per session scan A 261b15e3b92a

Subscribe to this mod's changes

browser-agent is an agent published in the GitHub repository TyrusRC/praetor (6 stars, last pushed yesterday), licensed Apache-2.0. It adds 32 tokens to every session and 731 once invoked, about $0.0001 per session on Opus 5.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.

Related

Other agents, from other repositories

ciso-reviewer

Business-impact gate. Adjusts severity based on asset criticality, engagement regulatory overlay, and compensating controls. Does NOT veto findings.

transilienceai/communitytools · 32 tokens

citation-verifier

Deterministic (not LLM). Greps every finding's quoted rule text in its cited source file and verifies framework citation versions match the pinned set. Mismatches → quarantine.

transilienceai/communitytools · 41 tokens

qa-tester

Specialized QA automation engineer. Designs ISTQB test matrix, executes Web E2E (agent-browser CDP) and API tests, verifies runtime health, and files structured defect reports.

datit309/supergraph · 41 tokens

agent-verdict-assessor

Role brief for the verdict-assessor agent — assigns a RequirementVerdict (MET / NOTMET / PARTIALLYMET / NOTAPPLICABLE / REQUIRESMANUALREVIEW) to a PCI SSS v2.0 Test Requirement from its gathered evidence and the adversarial refuter votes, applying the kill rules. Mounted by the workflow Assess/Verdict step.

transilienceai/communitytools · 82 tokens

smoke-sonnet

Use when one functional smoke flow must be walked in the running app as one persona, with a pass/fail per step. Needs the chrome-devtools MCP server. Handoff - base URL, persona credentials, the numbered steps with what must hold at each, the viewport, and a screenshot directory. Returns a step table; visual doubts…

yacb2/aidex · 105 tokens

verify-browser-opus

Use when a screen's appearance must be judged in the running app and no measurable property decides it (visual hierarchy, balance, "does it look right"). Needs the chrome-devtools MCP server. Handoff - the URL, the steps, the viewports, what a good result looks like, and a screenshot directory. Drives Chrome DevTools…

yacb2/aidex · 129 tokens