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/yurilopes/pydoll-mcp-serverWrote 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/yurilopes/pydoll-mcp-server/index)<a href="https://agentmods.dev/commands/yurilopes/pydoll-mcp-server/index"><img src="https://agentmods.dev/badge/commands/yurilopes/pydoll-mcp-server/index.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.00000 | $0.00538 |
| Opus 5 | $0.00000 | $0.00269 |
| Sonnet 5 | $0.00000 | $0.00108 |
| Haiku 4.5 | $0.00000 | $0.00054 |
Grade A, and why
index 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 8d 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 — 78 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Commands Overview
The Commands module provides high-level interfaces for interacting with Chrome DevTools Protocol (CDP) domains. Each command module corresponds to a specific CDP domain and provides methods to execute various browser operations.
Available Command Modules
Browser Commands
- Module:
browser_commands.py - Purpose: Browser-level operations and window management
- Documentation: Browser Commands
DOM Commands
- Module:
dom_commands.py - Purpose: DOM tree manipulation and element operations
- Documentation: DOM Commands
Input Commands
- Module:
input_commands.py - Purpose: Input event simulation (keyboard, mouse, touch)
- Documentation: Input Commands
Network Commands
- Module:
network_commands.py - Purpose: Network monitoring and request interception
- Documentation: Network Commands
Page Commands
- Module:
page_commands.py - Purpose: Page lifecycle management and navigation
- Documentation: Page Commands
Runtime Commands
- Module:
runtime_commands.py - Purpose: JavaScript execution and runtime management
- Documentation: Runtime Commands
Storage Commands
- Module:
storage_commands.py - Purpose: Browser storage access (cookies, local storage, etc.)
- Documentation: Storage Commands
Target Commands
- Module:
target_commands.py - Purpose: Target management and tab operations
- Documentation: Target Commands
Fetch Commands
- Module:
fetch_commands.py - Purpose: Network request interception and modification
- Documentation: Fetch Commands
Usage Pattern
Commands are typically accessed through the browser or tab instances:
from pydoll.browser.chromium import Chrome
# Initialize browser
browser = Chrome()
await browser.start()
# Get active tab
tab = await browser.get_active_tab()
# Use commands through the tab
await tab.navigate("https://example.com")
element = await tab.find(id="button")
await element.click()
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.
- 8d ago First seen · 78 lines · 0 tokens per session scan A eac9fa6474f7
index is a command published in the GitHub repository yurilopes/pydoll-mcp-server (1 stars, last pushed 24d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 538 tokens. 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 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.
can-i-use
Check browser support for web platform features against the project's browser targets.
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.
verify-pr
Verify a PR's frontend changes through browser automation.