flq
Fetch the web as lean, token-efficient text. HTML → .flq
Raw HTML wastes 70-90% of LLM tokens on markup. flq strips a page down to its content — headings, text, lists, tables, code — in a format that tokenizes tight and reads clean.
Install
Usage
|
curl-compatible flags
Extraction
Filters: headings code tables links img text
Agent workflow
|
Format
title: Page Title
url: https://example.com
lang: ja
desc: meta description
---
# heading
paragraph text
- list item
- nested item
> quote
@ https://link | link text
! https://img.png | alt text
table[3]{name,price,stock}:
Widget A,1200,45
Widget B,800,120
Gadget C,500,300
Prose stays markdown — LLMs parse it natively and every marker is one
token. Tables use schema-once TOON-style headers: field names are
declared once, rows stream as CSV. Links (@) and images (!) are
off by default; enable with -f links / -f img.
JSON output
tokens is an estimate (~4 ASCII chars or ~1.3 CJK chars per token).
As a library
use ;
let opts = Opts ;
let page = process?;
println!;
MCP server
flq doubles as a Model Context Protocol server, so agents like Claude Code can fetch and parse the web directly.
Tools: fetch_page, fetch_pages, crawl_site, head. See
docs/mcp.md for the full tool reference and setup, and
skills/flq/SKILL.md for an agent skill that teaches when
and how to reach for flq.
License
MIT