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.
git clone --depth 1 https://github.com/drisplabs/browser-mcpWrote 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/drisplabs/browser-mcp/generate-apple-doc)<a href="https://agentmods.dev/commands/drisplabs/browser-mcp/generate-apple-doc"><img src="https://agentmods.dev/badge/commands/drisplabs/browser-mcp/generate-apple-doc.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.00022 | $0.01839 |
| Opus 5 | $0.00011 | $0.00920 |
| Sonnet 5 | $0.00004 | $0.00368 |
| Haiku 4.5 | $0.00002 | $0.00184 |
Grade A, and why
generate-apple-doc 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 7d 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 — 201 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Generate Apple.com iPhone-to-Cart Tool Use Example
You are generating a documented tool-use example for Drisp Browser. You will drive a live browser session through apple.com's iPhone purchase flow, record every tool call and response, then produce a comprehensive markdown document with token analysis.
Output File
Write the final document to: docs/examples/tool-use-example-add-iphone-to-cart.md
Phase 1: Browser Automation
Execute the following steps using Drisp Browser tools. After EACH tool call, record:
- The tool name (without the
mcp__drisp-browser__prefix) - The exact input JSON you sent
- The full XML response you received (you will trim it later for the doc)
Step-by-step flow
-
navigatetohttps://www.apple.com- If a country/region selector overlay appears, dismiss it by clicking the close button.
-
clickthe "iPhone" link in the nav region. -
On the iPhone landing page,
clickthe "Buy, iPhone 17" link.- If iPhone 17 is not listed, use the latest available iPhone model and note this in the doc.
-
find_elementswithkind: "radio",region: "main",limit: 20to discover all configuration options. -
Configure the iPhone by clicking radio buttons in sequence. Each selection enables the next tier:
- Color: Select "Lavender" (or the first available color)
- Storage: Select "256GB"
- Trade-in: Select "No trade-in"
- Payment: Select "Buy" (full price)
- Carrier: Select "Connect to any carrier later" (unlocked)
- AppleCare: Select "No AppleCare coverage"
IMPORTANT: Wait for each tier to become enabled before clicking. If a radio button shows
enabled="false", you must first complete the preceding selection. -
clickthe "Add to Bag" button (look for it in theformregion withval="add-to-cart"). -
After the accessories upsell page loads,
scroll_pagedown to find the "Review Bag" button, thenclickit. -
On the Bag page, verify the iPhone is in the cart by checking:
- The nav shows "Shopping Bag with item count : 1"
- The main region contains the product name and "Check Out" button
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.
- 7d ago First seen · 201 lines · 22 tokens per session scan A 275f41d45473
generate-apple-doc is a command published in the GitHub repository drisplabs/browser-mcp (15 stars, last pushed 22d ago), licensed MIT. It adds 22 tokens to every session and 1,839 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
analyze
Analyze a webpage's structure using Actionbook's verified selectors and show available elements for scraping.
interactive-dev
Start a persistent interactive development session with natural language browser control, auto-error monitoring, and full dev tool access.
playbook
Manage Mochi playbooks (list, show, run, delete). Plays through the browser MCP tools.
intercept
HTTP sniffer for tandem's Chrome via CDP: captures request+response bodies (including HttpOnly, CSRF tokens, private APIs). Subcommands: start, show, clear, count.
cookies
Exports cookies from tandem's Chrome via CDP (includes HttpOnly/Secure). Filter with --domain . Formats: list (table, default), json, curl, headers, netscape.
naive-test
Drive the live app as a naive first-time user and report UX/behavior gaps before deploy.