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 skills add floomhq/moto --skill browsegit clone --depth 1 https://github.com/floomhq/motoWrote 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/skills/floomhq/moto/browse)<a href="https://agentmods.dev/skills/floomhq/moto/browse"><img src="https://agentmods.dev/badge/skills/floomhq/moto/browse.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.00069 | $0.00556 |
| Opus 5 | $0.00034 | $0.00278 |
| Sonnet 5 | $0.00014 | $0.00111 |
| Haiku 4.5 | $0.00007 | $0.00056 |
Grade A, and why
browse 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.
Browse Skill
Tool Selection
Three browser tool sets may be available. Use the right one for the task:
| Tool set | Use for |
|---|---|
| claude-in-chrome | Page reading, clicking, form filling, screenshots, navigation |
| chrome-devtools | Performance tracing, Lighthouse, network inspection |
| authenticated-browser | Playwright scripts, complex multi-step flows |
Default to claude-in-chrome for standard browse/read/click/screenshot tasks.
Common Patterns
Reading a web page
- Navigate to the URL
- Take a snapshot (a11y tree) to understand the page structure
- Extract the relevant content
- If content is incomplete, scroll or click to load more
Searching for information
- Navigate to a search engine or the site's search
- Enter the search query
- Read the results
- Navigate to the most relevant result
- Extract the needed information
Filling out a form
- Navigate to the page
- Take a snapshot to identify form fields
- Fill each field
- Verify the filled values before submitting
- Submit and confirm success
Handling blocked URLs
If WebFetch is blocked (paywalled, Reddit, etc.), try:
# Gemini fallback for web content
bash ~/.claude/scripts/gemini-fetch.sh "https://blocked-url.com"
Content Extraction Tips
- Use
get_page_textfor article-heavy pages (blog posts, documentation, news) - Use
take_snapshotfor interactive pages where you need to find elements - Use
take_screenshotto verify visual state - For JavaScript-heavy SPAs: wait for
networkidlebefore extracting
Privacy & Security
- Never enter passwords or sensitive credentials
- Be cautious with forms on unfamiliar sites
- Do not click "Accept all cookies" on cookie banners - decline or dismiss
- Do not download files without explicit user permission
Output Format
When reporting what was found:
- Summarize key information (don't reproduce entire pages)
- Quote specific short passages when precision matters (fewer than 15 words per quote)
- Provide the source URL
- Note if information may be outdated
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 · 69 tokens per session scan A 05b2b87316e2
browse is a skill published in the GitHub repository floomhq/moto (32 stars, last pushed 2mo ago), licensed MIT. It adds 69 tokens to every session and 556 once invoked, about $0.0003 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 skills, 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.
memstack-development-webapp-testing
Use when the user says 'write browser tests', 'test this page', 'playwright test', 'e2e test', 'end to end test', 'browser test', 'test the UI', or needs Playwright-based browser testing for a web application. Do NOT use for unit tests, API tests, or non-browser testing.
issue-triage
3-phase issue backlog management with audit, deep analysis, and validated triage actions. Use when triaging GitHub issues, sorting bug reports, cleaning up stale tickets, or detecting duplicate issues. Args: 'all' to analyze all, issue numbers to focus (e.g. '42 57'), 'en'/'fr' for language, no arg = audit only.
land-and-deploy
Merge PR, wait for CI, verify deploy, run canary. The complete landing pipeline.
self-assessment
Interactive skill assessment with personalized learning path generation.
investigate
Systematic root-cause debugging: find the cause before writing any fix.