DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to read only the needed part of long web pages with Donsetch

Use DonSeTch's token controls so an agent pulls a table of contents or one section, not the whole page.

  • Research
  • Intermediate
  • 15 minutes
  • From the README
  • Any agent

Authorization notice. Donsetch is dual-use. Only use it on software, sites and systems you own or have explicit permission to test.

Who it is forAn agent builder whose agent runs out of context when it reads long documentation or reports.

The problemFull page text fills the context window and wastes tokens on content the agent does not need.

The outcomeThe agent reads a table of contents, then fetches one section or a focused slice, and references search results by short tokens.

What you need first

  • npm or Homebrew to install the binary
  • An MCP-capable client such as Claude Code or Cursor, or the standalone CLI
  • Network access to the sites you want to read
  • Optional: a Chromium, Playwright-cached Chromium or Edge build for tier-2 browser escalation

Steps

  1. Run npm install -g donsetch
  2. Register the server in your agent's MCP config with the command donsetch and args ["mcp", "--supervised"]
  3. Call the fetch tool on the target URL with the toc option to list its sections
  4. Call the fetch tool again with the section or focus option for the part you need
  5. Use fetch S3-style references to fetch a search result by its short token

Prompt for your agent

Using the donsetch MCP server, fetch the table of contents of <URL>, then fetch only the section about <topic>. Return the section text and confirm the response is shorter than the full page.

Caveat. The toc, section and focus options are named in the README, so confirm their exact parameter names in the tool schema before relying on them.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page