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 commands/eigenweltlabs/legalwork/browser-setupgit clone --depth 1 https://github.com/eigenweltlabs/legalworkWrote 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/commands/eigenweltlabs/legalwork/browser-setup)<a href="https://agentmods.dev/commands/eigenweltlabs/legalwork/browser-setup"><img src="https://agentmods.dev/badge/commands/eigenweltlabs/legalwork/browser-setup.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.00011 | $0.00097 |
| Opus 5 | $0.00005 | $0.00048 |
| Sonnet 5 | $0.00002 | $0.00019 |
| Haiku 4.5 | $0.00001 | $0.00010 |
Grade A, and why
browser-setup 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.
What it actually says
Try browser automation in LegalWork right away.
IMPORTANT:
- Use the built-in LegalWork browser tools.
- In your first response, open
https://example.comand tell the user the page title. - If browser tools are unavailable, tell the user browser control is not available in this workspace and ask them to retry after LegalWork reloads.
Keep the response short and action-oriented.
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 · 14 lines · 11 tokens per session scan A 79bc1775e994
browser-setup is a command published in the GitHub repository eigenweltlabs/legalwork (98 stars, last pushed yesterday), licensed MIT. It adds 11 tokens to every session and 97 once invoked, about $0.0001 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-30.
Other commands, from other repositories
auto-browse
Auto-browse — learn, optimize, and graduate browser operations or web data-mining workflows.
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.
gh-issue-use-cypress
Like /gh-issue-use-browser, but pinned to the Cypress MCP — use when your project runs the Cypress MCP for browser automation. Example — /gh-issue-use-cypress "Composer > Save" saving toasts failure but the record persists.
qa
Smoke or browser-walk a running app. Report only. Do not implement. Do not merge.
can-i-use
Check browser support for web platform features against the project's browser targets.
verify-pr
Verify a PR's frontend changes through browser automation.