web_skeleton

Reads the web the way the other tools read code: a skeleton first, then only the section that matters.

Components

Capabilities

• search: search results, each with a title and a one-line summary.
• skeleton: a rendered page as headings, sections, links and form elements, each with a stable id.
• read: the full text of one section by id.
• click: follow a link or button by id and get the new page's skeleton.

How it works

Pages are rendered in headless Chromium through the Chrome DevTools Protocol, so content built by JavaScript is included. In typical use, a page that would cost 50,000 to 200,000 tokens as raw HTML becomes a skeleton of 500 to 3,000 tokens.

Safety in the sandbox

• Egress guard: all browser traffic, including redirects, frames, background scripts and websockets, goes through a guard that resolves every address itself.
• Private, loopback, link-local and cloud metadata addresses are refused, and the guard connects only to the exact address it checked, so DNS tricks cannot reach this machine or its network.
• Only https for public sites; file://, data: and similar schemes are blocked.