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/swimmwatch/cloakbrowser-mcp/performance-optimizationnpx skills add swimmwatch/cloakbrowser-mcp --skill performance-optimizationgit clone --depth 1 https://github.com/swimmwatch/cloakbrowser-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/skills/swimmwatch/cloakbrowser-mcp/performance-optimization)<a href="https://agentmods.dev/skills/swimmwatch/cloakbrowser-mcp/performance-optimization"><img src="https://agentmods.dev/badge/skills/swimmwatch/cloakbrowser-mcp/performance-optimization.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 | $0.00089 | $0.00451 |
| Opus 5 | $0.00044 | $0.00226 |
| Sonnet 5 | $0.00018 | $0.00090 |
| Haiku 4.5 | $0.00009 | $0.00045 |
Grade A, and why
performance-optimization 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 4d 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
Performance Optimization
- Read
AGENTS.mdand define the metric, representative input, environment, acceptable tradeoffs, success threshold, and correctness oracle. Use Prompt MCP for any material tradeoff or threshold the user has not supplied. - Record revision, operating system, architecture, Node and dependency versions, transport, browser/profile state, command, warm-up, repetitions, timings, resources, and variance.
- The repository has no dedicated benchmark script. Build a task-local,
reproducible measurement around real commands such as
npm run build,npm run dev -- <args>,node dist/cli.js <args>, the affected Vitest command,npm run package:verify, or Docker build/smoke. Use Node--cpu-profor--heap-profonly when it measures the identified path, and remove generated profiles unless the user requested artifacts. - Use CodeGraph before broad source search when indexed. Trace the measured bottleneck across CLI parsing, CloakBrowser resolution, temporary config, upstream child startup, MCP forwarding, HTTP session creation, filesystem, logging, packaging, or workflow layers.
- Change one justified factor at a time. Rerun the identical measurement and focused correctness tests; use enough repetitions to distinguish signal from noise.
- Run the affected type, lint, test, package, Docker, parity, and
npm run checkcommands before declaring success.
Report baseline, result, uncertainty, correctness evidence, security and compatibility safeguards, and rollback conditions. Never trade public contracts, cleanup, isolation, redaction, or safety for speed without explicit authorization.
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.
- 4d ago First seen · 34 lines · 89 tokens per session scan A 070513cff571
performance-optimization is a skill published in the GitHub repository swimmwatch/cloakbrowser-mcp (55 stars, last pushed 6d ago), licensed MIT. It adds 89 tokens to every session and 451 once invoked, about $0.0004 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
browser-search
Multi-engine web search (SearXNG) + browsing/scraping (Camofox, CloakBrowser). Use whenever you need to do web research.
chrome-orchestrator
Teach agents how to orchestrate Arthur and Gloria headless Chrome environments dynamically via the Python SDK and CLI.
x402
Set up Browser Use Cloud payments with x402 — pay per request from a crypto wallet (USDC on Base mainnet), no signup or API key. Two setups it works out up front — "just use it" (set up a wallet so you or Claude Code can run cloud browser tasks paid from the wallet — Claude writes and runs throwaway scripts, nothing…
opencli-autofix
Automatically fix broken OpenCLI adapters when commands fail. Load this skill when an opencli command fails — it guides you through collecting a trace artifact, patching the adapter, retrying, and filing an upstream GitHub issue after a verified fix. Works with any AI agent.
open-source
Documentation reference for writing Python code using the browser-use open-source library. Use this skill whenever the user needs help with Agent, Browser, or Tools configuration, is writing code that imports from browseruse, asks about @sandbox deployment, supported LLM models, Actor API, custom tools, lifecycle…
opencli-usage
Use at the start of any OpenCLI session — this is the top-level map of what opencli can do, how to discover adapters, what flags and output formats are universal, and which specialized skill to load next. Point here when an agent asks "what can opencli do?" or "how do I find the right command?".