Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add dodobrands/ai-hub/plugin install buildinWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/commands/dodobrands/ai-hub/read-page)<a href="https://agentmods.dev/commands/dodobrands/ai-hub/read-page"><img src="https://agentmods.dev/badge/commands/dodobrands/ai-hub/read-page.svg" alt="Measured on agentmods" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00022 | $0.01076 |
| Opus 5 | $0.00011 | $0.00538 |
| Sonnet 5 | $0.00004 | $0.00215 |
| Haiku 4.5 | $0.00002 | $0.00108 |
Grade A, and why
read-page scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 8d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 110 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Read Page — чтение страницы Buildin (UI API)
Читает страницу из Buildin.ai и выводит содержимое как markdown. UI API возвращает все блоки за один запрос.
Константы
Каталог скриптов резолвится так, чтобы команда работала из любого репозитория (standalone-клон, subtree-overlay, marketplace-install). Выполни строку-резолвер перед вызовом скриптов; если bash-блоки запускаются отдельными shell'ами и переменная между ними не сохраняется — повтори её в начале нужного блока.
# resolve-buildin-dir:start — первый существующий из кандидатов: плагин-кеш → overlay → standalone
BUILDIN_SCRIPTS=$(ls -d "${CLAUDE_PLUGIN_ROOT:-/nope}/scripts" "$PWD"/integrations/*/integrations/buildin/scripts "$PWD"/integrations/buildin/scripts 2>/dev/null | head -1)
# resolve-buildin-dir:end
BUILDIN_SPACE_ID = YOUR_SPACE_ID
Известные корневые страницы
Root Page = YOUR_ROOT_PAGE_ID
Входные параметры
Аргумент: $ARGUMENTS
Поддерживаемые форматы:
- URL:
https://buildin.ai/<space_id>/<page_id> - UUID:
2a904afe-42e9-4ebd-a94e-f6fe0cbacf58 - Поисковый запрос: любой текст без UUID — ищет через UI Search API
Workflow
Фаза 0: Проверь авторизацию
bash "$BUILDIN_SCRIPTS/buildin-login.sh" check
Если error:* — запусти /ai-hub:buildin-login для логина.
Фаза 1: Определить page_id
- Если аргумент содержит UUID (8-4-4-4-12 hex) — это page_id, извлеки его
- Если аргумент — текст без UUID — это поисковый запрос. UI Search API — КРАЙНИЙ способ (качество низкое, результаты часто нерелевантны, к тому же поиск scoped на конкретный space). Порядок:
- Сначала ищи в shadow-индексе (мгновенно):
bash "$BUILDIN_SCRIPTS/buildin-shadow.sh" search "<query>" - Если известна базовая страница по теме — обходи дерево от неё вглубь (попутно наполняет shadow-индекс для будущих поисков):
bash "$BUILDIN_SCRIPTS/buildin-nav.sh" children "<base_page_id>" - Только если выше ничего не дало — UI Search API (укажи нужный space_id, иначе ищет не там):
bash "$BUILDIN_SCRIPTS/buildin-nav.sh" search "<query>" "<space_id>"
- Сначала ищи в shadow-индексе (мгновенно):
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 8d ago First seen · 110 lines · 22 tokens per session scan A 332bea902869
read-page is a command published in the GitHub repository dodobrands/ai-hub (6 stars, last pushed 7d ago), licensed MIT. It adds 22 tokens to every session and 1,076 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other commands, from other repositories
Captures the current page in tandem's Chrome as a PDF (if headless Chrome) or full-page PNG screenshot (in normal tandem mode). Saves to /.claude/tandem/output/.
browse
Generate a single-file markdown browser HTML — tree sidebar + marked.js render. Scans project docs/ + /.claude/{plans,projects} by default.
view-document
Open Trio wiki in the browser, rooted at the current working directory. Auto-invoke when the user asks to open their Markdown wiki, browse notes, or view the current folder as a wiki.
scrape
Scrape one or more web pages to clean Markdown.
auto-browse
Auto-browse — learn, optimize, and graduate browser operations or web data-mining workflows.
brand-generate
Generate an on-brand document from a saved Brand Profile.