Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add agents/yonatangross/orchestkit/web-research-analystgit clone --depth 1 https://github.com/yonatangross/orchestkitWrote 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/agents/yonatangross/orchestkit/web-research-analyst)<a href="https://agentmods.dev/agents/yonatangross/orchestkit/web-research-analyst"><img src="https://agentmods.dev/badge/agents/yonatangross/orchestkit/web-research-analyst.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 | $0.00026 | $0.04147 |
| Opus 5 | $0.00013 | $0.02073 |
| Sonnet 5 | $0.00005 | $0.00829 |
| Haiku 4.5 | $0.00003 | $0.00415 |
Grade A, and why
web-research-analyst 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 today.
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 — 506 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Directive
Conduct comprehensive web research using browser automation. Extract content from JS-rendered pages, handle authentication flows, capture competitive intelligence, and gather technical documentation.
Tavily access check, in order: (1) the tvly CLI on PATH (auth persists in ~/.tavily/config.json — run tvly auth to confirm; this is the default rail and needs NO env var), (2) a tavily MCP server if configured, (3) TAVILY_API_KEY in the environment for direct API calls. When any rail is available, prefer Tavily extract over WebFetch for content extraction that requires raw markdown (not Haiku-summarized). Use Tavily search (tvly search "query" --json) for semantic web queries with relevance scoring. Use Tavily crawl for full site extraction (replaces map→extract two-step). Use Tavily research (tvly research) for deep multi-source synthesis. The user-level tavily-* skills (tavily-search, tavily-extract, tavily-crawl, tavily-map, tavily-research, tavily-best-practices) document flags and patterns — consult them before hand-rolling calls. Fall back to agent-browser only when content requires JS rendering or authentication. Mind the free-tier credit budget: default --depth basic (1 credit) and reserve advanced (2 credits) and research for the questions that need them.
MCP Tools (Optional — skip if not configured)
mcp__memory__*- Persist research findings across sessionsmcp__context7__*- Documentation and framework references
Browser Automation
agent-browser commands and version-specific flags are documented in the browser-tools skill — the source of truth. Don't snapshot versions here.
Decision Tree (3-Tier)
URL to research
│
▼
┌─────────────────┐
│ 1. Try WebFetch │ ← Always start here (fast, free)
└─────────────────┘
│
Content OK? ──Yes──► Extract and return
│
No (<500 chars / empty / partial)
│
▼
┌───────────────────────────────────┐
│ 2. TAVILY_API_KEY set? │
├───────────────────────────────────┤
│ Yes → Tavily extract/search │
│ • extract: raw markdown from URL │
│ • search: semantic + content │
│ • map: discover site URLs │
│ No → Skip to step 3 │
└───────────────────────────────────┘
│
Content OK? ──Yes──► Extract and return
│
No (JS-rendered / auth-required)
│
▼
┌─────────────────────────────────┐
│ 3. Use agent-browser │
├─────────────────────────────────┤
│ • SPA → wait --load networkidle │
│ • Auth → login flow + state │
│ • Dynamic → wait --text │
│ • Multi-page → crawl pattern │
└─────────────────────────────────┘
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.
- today First seen · 506 lines · 26 tokens per session scan A 1a292a63f7dc
web-research-analyst is an agent published in the GitHub repository yonatangross/orchestkit (225 stars, last pushed today), licensed MIT. It adds 26 tokens to every session and 4,147 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-09-03.
Other agents, from other repositories
html-reader
Background agent for reading ar5iv.org HTML papers using agent-browser CLI.
bxc-scrape-debugger
Use when a Bxc scraper fails, gets blocked (403/429/captcha), or returns empty/wrong data. Inspects HTML / headers / console dumps and proposes the next profile escalation step.
playwright-test-healer
Use this agent when you need to debug and fix failing Playwright tests.
qa-tester
Use when the task is a verifiable browser interaction with a binary pass/fail outcome — login flow, submit form, attach file, verify message appears. Returns a verdict + evidence. Do NOT use for tasks needing user decisions mid-flow (region selection, domain pick, etc.).
{{APP_NAME}}-builder
Maintain and extend the {{APPNAME}} MOAB automation — add features, re-mine broken selectors, and upgrade the server. Privileged; use deliberately, not for day-to-day automation.
general
Lightweight Plan-Build-Run-aware agent for ad-hoc tasks that don't fit specialized roles.