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/dom)<a href="https://agentmods.dev/commands/yurilopes/pydoll-mcp-server/dom"><img src="https://agentmods.dev/badge/commands/yurilopes/pydoll-mcp-server/dom.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.00421 |
| Opus 5 | $0.00000 | $0.00211 |
| Sonnet 5 | $0.00000 | $0.00084 |
| Haiku 4.5 | $0.00000 | $0.00042 |
Grade A, and why
dom 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.
What it actually says
DOM Commands
DOM commands provide comprehensive functionality for interacting with the Document Object Model of web pages.
Overview
The DOM commands module is one of the most important modules in Pydoll, providing all the functionality needed to find, interact with, and manipulate HTML elements on web pages.
::: pydoll.commands.dom_commands options: show_root_heading: true show_source: false heading_level: 2 filters: - "!^_" - "!^__"
Usage
DOM commands are used extensively by the WebElement class and element finding methods:
from pydoll.commands.dom_commands import query_selector, get_attributes
from pydoll.connection.connection_handler import ConnectionHandler
# Find element and get its attributes
connection = ConnectionHandler()
node_id = await query_selector(connection, selector="#username")
attributes = await get_attributes(connection, node_id=node_id)
Key Functionality
The DOM commands module provides functions for:
Element Finding
query_selector()- Find single element by CSS selectorquery_selector_all()- Find multiple elements by CSS selectorget_document()- Get the document root node
Element Interaction
click_element()- Click on elementsfocus_element()- Focus elementsset_attribute_value()- Set element attributesget_attributes()- Get element attributes
Element Information
get_box_model()- Get element positioning and dimensionsdescribe_node()- Get detailed element informationget_outer_html()- Get element HTML content
DOM Manipulation
remove_node()- Remove elements from DOMset_node_value()- Set element valuesrequest_child_nodes()- Get child elements
!!! tip "High-Level APIs"
While these commands provide powerful low-level access, most users should use the higher-level WebElement class methods like click(), type_text(), and get_attribute() which use these commands internally.
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 · 58 lines · 0 tokens per session scan A cc3d35ad6eee
dom 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 421 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
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.
capture_full_page
Capture a full-page (entire scrollable page, beyond the viewport) or single-element screenshot through the Chrome debugger and save it under screenshots/. Unlike takescreenshot (viewport only, no debugger), this uses CDP to render the whole page or a specific element.