Borrowing it
Nothing to install: this file belongs to malwarebo/nyrve. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/malwarebo/nyrve/main/.agents/skills/launch/SKILL.mdgit clone --depth 1 https://github.com/malwarebo/nyrveWrote 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/malwarebo/nyrve/launch)<a href="https://agentmods.dev/skills/malwarebo/nyrve/launch"><img src="https://agentmods.dev/badge/skills/malwarebo/nyrve/launch/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/malwarebo/nyrve/launch"><img src="https://agentmods.dev/badge/skills/malwarebo/nyrve/launch.svg" alt="Reviewed on agentmods" width="80" 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.00080 | $0.03650 |
| Opus 5.5 | $0.00032 | $0.01460 |
| Sonnet 5.5 | $0.00016 | $0.00730 |
| Haiku 4.5 | $0.00008 | $0.00365 |
Grade A, and why
launch 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 1mo 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 — 351 lines — stays where its author put it; the contents beside it link to each section on GitHub.
VS Code Automation
Automate VS Code (Code OSS) using agent-browser. VS Code is built on Electron/Chromium and exposes a Chrome DevTools Protocol (CDP) port that agent-browser can connect to, enabling the same snapshot-interact workflow used for web pages.
Prerequisites
agent-browsermust be installed. It's listed in devDependencies — runnpm installin the repo root. Usenpx agent-browserif it's not on your PATH, or install globally withnpm install -g agent-browser.- For Code OSS (VS Code dev build): The repo must be built before launching.
./scripts/code.shruns the build automatically if needed, or setVSCODE_SKIP_PRELAUNCH=1to skip the compile step if you've already built. - CSS selectors are internal implementation details. Selectors like
.interactive-input-part,.interactive-input-editor, and.part.auxiliarybarused inevalcommands are VS Code internals that may change across versions. If they stop working, useagent-browser snapshot -ito re-discover the current DOM structure.
Core Workflow
- Launch Code OSS with remote debugging enabled
- Connect agent-browser to the CDP port
- Snapshot to discover interactive elements
- Interact using element refs
- Re-snapshot after navigation or state changes
📸 Take screenshots for a paper trail. Use
agent-browser screenshot <path>at key moments — after launch, before/after interactions, and when something goes wrong. Screenshots provide visual proof of what the UI looked like and are invaluable for debugging failures or documenting what was accomplished.Save screenshots inside a timestamped subfolder so each run is isolated and nothing gets overwritten:
# Create a timestamped folder for this run's screenshots SCREENSHOT_DIR="/tmp/code-oss-screenshots/$(date +%Y-%m-%dT%H-%M-%S)" mkdir -p "$SCREENSHOT_DIR" # Save a screenshot (path is a positional argument — use ./ or absolute paths) # Bare filenames without ./ may be misinterpreted as CSS selectors agent-browser screenshot "$SCREENSHOT_DIR/after-launch.png"
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.
- 1mo ago First seen · 351 lines · 80 tokens per session scan A 4aa06d44cbba
launch is a skill published in the GitHub repository malwarebo/nyrve (5 stars, last pushed 4mo ago), licensed MIT. It adds 80 tokens to every session and 3,650 once invoked, about $0.0003 per session on Opus 5.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-31.
Other skills, from other repositories
verify-bb
Verify BB user journeys in an isolated source dev app using dev-browser@next and the matching source CLI. Use after BB feature changes or when asked to verify or smoke-test BB. The feature map covers core UI and agent interfaces, every repository plugin, desktop, mobile, and hosted services; select the affected…
browser-automation
Use the Browser Automation BB plugin to inspect and automate persistent browser pages in an explicit desktop or local headless session. Use for browser navigation, snapshots, clicking, forms, and verification screenshots.
agent-annotations
Create or edit element annotations in desktop Browser tabs, or update saved annotation comments through the plugin RPC.
create-verification-skill
Create a repo-local verification skill and exhaustive feature map for driving a real app through its UI, CLI, or API. Use for "create a verification skill", "make a verify skill for this repo", or "document how agents can verify this app".
maintain-verification-skill
Audit an existing verification skill and feature map against source and the running app, then repair proven documentation or harness drift. Use for "maintain the verification skill", "audit the verify skill", or "refresh the verification feature map".
javascript-sandbox
Best practices for using the stagewise built-in JavaScript sandbox. Explains how to access APIs for browser debugging/interaction, use external dependencies, file system access, running mini-apps, etc.