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 skills/kivo360/omoios/browser-usenpx skills add kivo360/OmoiOS --skill browser-usegit clone --depth 1 https://github.com/kivo360/OmoiOSWrote 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/kivo360/omoios/browser-use)<a href="https://agentmods.dev/skills/kivo360/omoios/browser-use"><img src="https://agentmods.dev/badge/skills/kivo360/omoios/browser-use.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.00047 | $0.03280 |
| Opus 5 | $0.00023 | $0.01640 |
| Sonnet 5 | $0.00009 | $0.00656 |
| Haiku 4.5 | $0.00005 | $0.00328 |
Grade A, and why
browser-use 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 6d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- browser-use — 100% identical, 2 lines differ
How it starts
The opening of the file, as written. The whole thing — 406 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Browser Automation with browser-use CLI
The browser-use command provides fast, persistent browser automation. It maintains browser sessions across commands, enabling complex multi-step workflows.
Installation
# Run without installing (recommended for one-off use)
uvx "browser-use[cli]" open https://example.com
# Or install permanently
uv pip install "browser-use[cli]"
# Install browser dependencies (Chromium)
browser-use install
Quick Start
browser-use open https://example.com # Navigate to URL
browser-use state # Get page elements with indices
browser-use click 5 # Click element by index
browser-use type "Hello World" # Type text
browser-use screenshot # Take screenshot
browser-use close # Close browser
Core Workflow
- Navigate:
browser-use open <url>- Opens URL (starts browser if needed) - Inspect:
browser-use state- Returns clickable elements with indices - Interact: Use indices from state to interact (
browser-use click 5,browser-use input 3 "text") - Verify:
browser-use stateorbrowser-use screenshotto confirm actions - Repeat: Browser stays open between commands
Browser Modes
browser-use --browser chromium open <url> # Default: headless Chromium
browser-use --browser chromium --headed open <url> # Visible Chromium window
browser-use --browser real open <url> # User's Chrome with login sessions
browser-use --browser remote open <url> # Cloud browser (requires API key)
- chromium: Fast, isolated, headless by default
- real: Uses your Chrome with cookies, extensions, logged-in sessions
- remote: Cloud-hosted browser with proxy support (requires BROWSER_USE_API_KEY)
Commands
Navigation
browser-use open <url> # Navigate to URL
browser-use back # Go back in history
browser-use scroll down # Scroll down
browser-use scroll up # Scroll up
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.
- 6d ago First seen · 406 lines · 47 tokens per session scan A 1362b769c8fe
browser-use is a skill published in the GitHub repository kivo360/OmoiOS (76 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 47 tokens to every session and 3,280 once invoked, about $0.0002 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
self-awareness
Use when the user asks about Archie itself — what Archie is, how it works, what it can or cannot do, what agents or domains exist, how plugins work, how requests get handled, why something behaves a certain way, what integrations are available, or whether Archie can change itself. Triggers on phrases like "what can…
archie-e2e
Boot a live Archie instance from the current branch, drive E2E scenarios headlessly through the archie-debug MCP (nonce → createtask → waitfortask → approve), capture per-scenario evidence files, and tear down cleanly. Use for Forge Stage 4 QA, verifying a branch against a live instance, running the basic or edit-mode…
openspec-explore
Enter explore mode - a thinking partner for exploring ideas, investigating problems, and clarifying requirements. Use when the user wants to think through something before or during a change.
writing-plugins
Read this before authoring or substantially changing a plugin, agent, or skill for Archie. It's the conceptual playbook for building plugins that fit Archie's multi-agent, single-orchestrator model — what a plugin must respect, why every plugin usually needs an orchestrator-facing skill, and how to think about agents…
triggers
Set up, list, or manage triggers — persistent "do Y when X happens" rules. Use when someone asks Archie to do something on a schedule ("every weekday at 9am…", "every morning post…", "remind the channel weekly…"), to react to new messages in a channel ("whenever someone posts X in.
thread-conduct
Use before posting anywhere outside this task's own thread, or when deciding how much to post inside it. Covers keeping one task in one thread, what to do with a finding that belongs to another team, when a cross-channel post is allowed and how small it must be, how much traffic a thread should carry, and how to…