browser-and-passwords
Skill204 starsChanged 8 days agoMITView on GitHub
Use when verifying browser sessions (native profiles, CDP boundary, editing, navigation, agent cursors, downloads), passkeys, Chrome extension pairing, site-cookie admission and sign-in delivery, the native Passwords broker, import worker and Swift/TypeScript wire fixtures, or saved-login leases, browser fills and sealed app delivery.
In this repository9 other files it gives its agents.
- AGENTS.mdAGENTS.md
- agent-phoneSkill
- desktop-buildsSkill
- mac-guiSkill
- mobileSkill
- run-agent-evalsSkill
- setupSkill
- testingSkill
- upgrade-enginesSkill
The file
We split this skill into the rules it gives an agent
6 rules. About 0 are common, 4 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 15
Stop everything you start by captured PID or serial, even after a failure.
- Very specific: line 16
Never drive the host screen: GUI and Electron checks run only in the VM (pnpm test:vm).
- Distinctive: line 17
Never read or operate signing keys, Apple accounts or release credentials.
- Distinctive: line 18
Never use a person's real profile, credentials, saved passwords, Messages or personal stores.
- Very specific: line 19
Never touch the live install: ~/Library/Application Support/Opensteer, ~/Opensteer, Opensteer Beta.
- Distinctive: line 22
Use disposable Chromium profiles, roots and test accounts.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Browser and passwords
Verification for browser sessions and Opensteer Passwords. Browser sessions and Opensteer Passwords hold the rules these checks protect.
Safety rules
- Devices have one owner: never take another task's simulator, emulator, USB phone or VM slot.
- Stop everything you start by captured PID or serial, even after a failure; never kill by name.
- Never drive the host screen: GUI and Electron checks run only in the VM (
pnpm test:vm). - Never read or operate signing keys, Apple accounts or release credentials.
- Never use a person's real profile, credentials, saved passwords, Messages or personal stores.
- Never touch the live install:
~/Library/Application Support/Opensteer,~/Opensteer,Opensteer Beta. - Skipped, blocked or unrun checks are unverified, never passed.
- Use disposable Chromium profiles, roots and test accounts; keep saved values out of reports.
Procedures
- Browser sessions: editing, downloads, CDP boundary, native profiles.
- Passkeys: flag, routing tests, VM journey.
- Chrome sign-ins: extension pairing and delivery.
- Passwords: Swift broker, wire fixtures, saved logins.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.