菜单
Use when HYDRA tasks need Node.js-first terminal browsing, deterministic page extraction, and evidence JSON output that can be routed into hydra swarm workflows.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Boot, recover, tune, and verify the SCBE Android emulator phone lane for AetherCode and Polly Pad. Use when Codex needs to operate the `SCBE_Pixel_6_API35` emulator, repair stale lock state, resize the phone surface, or prove the current lane state from local artifacts.
Navigate arXiv papers and topic searches through AetherBrowser for research extraction workflows. Use when collecting abstracts, paper metadata, and evidence snapshots from arxiv.org.
Navigate GitHub repositories, pull requests, issues, and settings through AetherBrowser tentacle routing. Use when tasks require browser-based GitHub movement, page evidence capture, or coordinated lane assignment with playwriter or playwright.
Navigate Hugging Face models, datasets, and spaces through AetherBrowser for research, validation, and publishing workflows. Use when inspecting repo cards, files, docs, and leaderboard surfaces in browser mode.
Navigate Notion workspace pages in AetherBrowser for knowledge retrieval and workspace coordination tasks. Use when locating pages, databases, or section paths in browser mode before API operations.
Operate AetherBrowser as the primary online task surface across search, GitHub, Codespaces, research, Notion, Hugging Face, Shopify, and general web work. Use when Codex should drive a real browser session first, coordinate with built-in search or fetch tools second, capture page-state proof, and keep online work inside the SCBE browser lane instead of defaulting to generic web automation.
| name | hydra-node-terminal-browsing |
| description | Use when HYDRA tasks need Node.js-first terminal browsing, deterministic page extraction, and evidence JSON output that can be routed into hydra swarm workflows. |
Use this skill for fast terminal-first web/repo browsing in HYDRA workflows when you need deterministic, auditable output instead of conversational browsing.
This skill is optimized for the HYDRA 3-gap surfaces:
hydra/browsers.pyhydra/swarm_browser.pyhydra/cli_swarm.pyTrigger this skill when the user asks to:
Do not use this skill for deep JavaScript rendering correctness testing. For full rendering, use HYDRA Playwright backend directly.
node C:\Users\issda\.codex\skills\hydra-node-terminal-browsing\scripts\hydra_terminal_browse.mjs --url "https://example.com" --out "artifacts\page_evidence.json"
Output is structured JSON with:
url, resolved_url, statustitletext_excerptlinks[]metrics and fetched_atpython -m hydra.cli_swarm --status
python -m hydra.cli_swarm --dry-run "research SCBE-AETHERMOORE on GitHub"
python -m hydra.cli_swarm --provider local --backend playwright "navigate to example.com and summarize"
python -m hydra.cli_swarm --provider hf --model mistralai/Mistral-7B-Instruct-v0.3 "find latest PQC migration notes"
hydra_terminal_browse.mjs.python -m hydra.cli_swarm ....--dry-run before live browser actions.--out.When using terminal browse for governance/evidence tasks, persist output in this shape:
{
"url": "https://...",
"resolved_url": "https://...",
"status": 200,
"title": "...",
"text_excerpt": "...",
"links": ["https://..."],
"metrics": {
"html_chars": 0,
"text_chars": 0,
"link_count": 0,
"truncated": false
},
"fetched_at": "2026-02-22T00:00:00Z"
}
--dry-run first.hydra_terminal_browse.mjs: Node CLI for deterministic terminal browsing and evidence JSON export.hydra-browser-surfaces.md: quick map of HYDRA browser-related modules and test targets.