List a page's links
Where does this page link to?
Have Browser-Q pull every link from a page with a ready-made template, then count and read them yourself.
What you get: every link on a live page, with its text and where it goes, read by a real browser.
Ask Quox
Section titled “Ask Quox”Name the template and the page:
Using the ready-made page links extraction template, pull every link from https://example.com.
▤ AOCL │ L1 identity complete · allowed · 1ms
▤ AOCL │ L3 policy gate complete · proceed · 12ms
◐ DELEGATE │ delegate_to_agent agent_id=browser-q ✔ DELEGATE │ delegate_to_agent agent_id=browser-q │ 2 tools used, 2 tool outcomes · 32.6s
⛓ AEE │ envelope opened · ops.tool · delegate_to_agent ok
⛓ AEE │ envelope opened · stream_success
Page extraction is BrowserQ's job, so I'll hand it over with the template named. The page links template found exactly one link on the page (source: browser_extract_template). Steps 1. I opened https://example.com. It redirected to https://example.com/ (just a trailing slash added), page title "Example Domain" (source: browser_navigate). 2. I ran the page links template on that page. It returned a count of 1 (source: browser_extract_template). Links found Text │ href ───────────┼────────────────────────────────────── Learn more │ https://iana.org/help/example-domains The link has no title or rel attribute. The page's accessibility tree also shows only this one link, so the result looks complete (source: browser_navigate). If you want to keep this result, its extraction id is d9d438b466cbe1d55ebce932 . The page text says the domain is only for documentation examples and shouldn't be used for testing or monitoring. A one-off extraction like this is fine, but I wouldn't set up a recurring monitor against it. Tools used: browser_navigate, browser_extract_template BrowserQ found one link on example.com, "Learn more", which points to https://iana.org/help/example-domains.
50.3s · 1 tool · 0 approvals
quox.✔ Machine verified against the CLI on 2 Nov 2026 · test report mvzv5j
Quox handed the job to Browser-Q, the browser specialist. Browser-Q opened the page, ran its page links template, and checked the count against the page’s accessibility tree before answering.
Do it yourself
Section titled “Do it yourself”1. Count the links
Section titled “1. Count the links”quox qlarity read with the count inspector counts the elements that match a selector:
quox qlarity read https://example.com --inspector count --selector a🔍 QLARITY: https://example.com/ (200) Example Domain count:12. Read where a link goes
Section titled “2. Read where a link goes”The attribute inspector reads one attribute of the first match:
quox qlarity read https://example.com --inspector attribute --selector a --name href🔍 QLARITY: https://example.com/ (200) Example Domain attribute:"https://iana.org/help/example-domains"Narrow the selector to read one part of a page, for example nav a for the menu or footer a for the footer.
What just happened
Section titled “What just happened”Both routes opened the page in a browser on your Quox and only read it. Nothing was clicked or submitted, so no approval was needed.
Check it yourself
Section titled “Check it yourself”The Browser-Q answer and the two reads agree: one link, pointing at https://iana.org/help/example-domains. quox qlarity inspectors lists every read you can run the same way.
Reading changes nothing, so there is nothing to undo.