oya-browser SKILL.md skillA
oya-browser from oyadotai/oya-browser is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add oyadotai/oya-browser/oya-browser@git:20260925.7541816Pins git:20260925.7541816 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- oyadotai/oya-browser
- Path
skills/oya-browser/SKILL.md- Versions recorded
- 4
- Latest version
- git:20260925.7541816, committed Sep 25, 2026
- First version recorded
- Sep 21, 2026
- Size
- 8,525 bytes
- Repository stars
- 354
- License
- a license file GitHub does not identify
Drive real Chrome browsers through Oya Browser. Start a browser on Oya Cloud, Browserbase, Steel, Anchor or Browser Use under a persistent persona, read pages as markdown with numbered elements, click and type, solve CAPTCHAs and MFA, and hand off to a human when needed. Use when the user asks to browse a site, automate a web task, fill a form, log in somewhere, scrape, or run several browsers at once. Works through the @oya-ai/browser SDK (which signs itself up and pairs the user's desktop…
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Oya Browser
Oya gives you real Chrome browsers behind one API. Each browser runs as a **persona**: a fingerprint, cookie jar and proxy that stay the same across runs, so a site sees the same device every time. You drive it by page structure, not selectors: read the page as markdown with numbered elements, then act on the numbers.
## Setup (once)
Prefer the SDK (Node 22.3+). It needs nothing from the user but their email:
```ts
import { Oya } from "@oya-ai/browser"; // npm install @oya-ai/browser
// No OYA_API_KEY and nothing in ~/.oya/config.json? Get a key of your own (saved there).
const { claimUrl } = await Oya.signup({ email: "<the user's email>" });
const oya = new Oya();
const browser = await oya.desktop.connect(); // the user's own browser, with their logins
```
`desktop.connect()` pairs the Oya desktop app when it is not connected yet: tell the user to click Connect in the Oya window and keep "Also import my logins" ticked (on macOS, allow "Chrome Safe Storage"). If the app is missing, the error gives the download link. `claimUrl` matters only for Oya Cloud browsers: send it to the user then.
MCP tools, when the user already set them up, work too:
…Read the whole file at its exact version.
How to install
mdr add oyadotai/oya-browser/oya-browser@sha256:c47aa13fbdc108f4The line at the top of this page pins the label git:20260925.7541816, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_fic7k63poln4czxi)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 4 versions of this file, between Sep 21, 2026 and Sep 25, 2026, about one every day.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260925.7541816 latest | 2026-09-25 | 7541816 | 8,525 B | A | view · diff |
| git:20260922.49189c7 | 2026-09-22 | 49189c7 | 7,846 B | A | view · diff |
| git:20260921.cde2153 | 2026-09-21 | cde2153 | 6,931 B | A | view · diff |
| git:20260921.1842a93 | 2026-09-21 | 1842a93 | 6,943 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (8525 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
oyadotai/oya-browser · 354 stars · license a license file GitHub does not identify · pushed 2026-10-20 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_fic7k63poln4czxi GET https://markdownregistry.com/api/v1/resolve?ref=oyadotai/oya-browser/oya-browser GET https://markdownregistry.com/api/v1/blob/c47aa13fbdc108f45861027b5dc24f400e884cc7ee606c4d218492a0bb97e3c2
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.