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 skills add runxhq/runx --skill web-searchgit clone --depth 1 https://github.com/runxhq/runxWrote 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/skills/runxhq/runx/web-search)<a href="https://agentmods.dev/skills/runxhq/runx/web-search"><img src="https://agentmods.dev/badge/skills/runxhq/runx/web-search/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/runxhq/runx/web-search"><img src="https://agentmods.dev/badge/skills/runxhq/runx/web-search.svg" alt="Reviewed on agentmods" width="80" 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.00034 | $0.00447 |
| Opus 5.5 | $0.00014 | $0.00179 |
| Sonnet 5.5 | $0.00007 | $0.00089 |
| Haiku 4.5 | $0.00003 | $0.00045 |
Grade A, and why
web-search 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 5d 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 — 44 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Web search
Discover sources for a specific question. The initial search runner uses the
selected Exa account for one query and at most 20 results. It normalizes source
identity, removes exact duplicate URLs, rejects malformed non-web candidates
and preserves the provider operation alongside the result. It does not silently
choose another provider, execute extra queries, fetch full pages or write a
research conclusion. Exa is the initial executable backend; additional backends
need their own declared operations and result mapping.
Search procedure
Choose one concrete information need per query. Include the relevant entity, decision and discriminating terms. Prefer direct evidence: official documentation, first-party announcements, original reports or research. Use domain restrictions when the task requires authoritative sources. Use publication-date bounds for a time-sensitive question, remembering that a publication date is not necessarily the event date. Do not add filters that exclude the contrary evidence you need.
Limit queries and results to the caller's actual budget. Search may consume paid credits. The result includes reported cost when available; missing cost remains unknown. The result cap is not a monetary spending limit. This package adds no billing authority or automatic retry after an uncertain paid request.
Result and composition
search_result contains the query, provider request ID, usable source candidates,
discard counts and reported cost. provider_operation retains the exact native
provider evidence and account binding. An empty provider result returns
no_results; a nonempty response with no usable candidates returns
unusable_results. Neither means the question has been researched exhaustively.
Titles, dates and any returned excerpt are discovery metadata, not verified claims
or full page content. Fetch selected URLs through web-fetch and feed the actual
retrieved packets to research. Check contradictions, source diversity and
coverage before drawing conclusions. research over supplied evidence does not
perform fresh discovery by itself. Reuse adequate existing evidence rather than
repeating a paid search.
What ships with it
9 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- fixtures/bounded-discovery.yaml 1.8 KB
- fixtures/composes-in-graph.yaml 110 B
- fixtures/empty-discovery.yaml 867 B
- fixtures/support/composed.graph 234 B
- fixtures/unusable-candidates.yaml 1.0 KB
- references/catalog.md 142 B
- run.yaml 3.8 KB
- web-search.mjs 2.5 KB runs code
- web-search.test.mjs 2.4 KB runs code
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.
- 5d ago First seen · 44 lines · 34 tokens per session scan A 4e2505d1a08e
web-search is a skill published in the GitHub repository runxhq/runx (103 stars, last pushed today), licensed Apache-2.0. It adds 34 tokens to every session and 447 once invoked, about $0.0001 per session on Opus 5.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-10-12.
Other skills, from other repositories
dd-synthesis
Synthesize findings from multiple specialist agents into a coherent investment recommendation. Use when combining reports from 9+ specialist agents into a single decision document.
dd-report-format
Standard output format for due diligence analysis reports. Use when producing your final analysis to ensure consistency across all specialist agents.
dd-risk-scoring
Calculate weighted risk scores from specialist agent reports. Use when synthesizing multiple due diligence reports into an overall investment risk assessment.
dd-sourcing
Document sources properly for due diligence reports. Use when citing any external data, ensuring full traceability and auditability of findings.
dd-verification
Verify claims in pitch decks and founder statements using multiple independent sources. Use when analyzing any claim about market size, traction, team background, or competitive positioning.
codew-release-qa-sweep
Use before claiming Codewhale release work is done: run the full gate sweep and list the manual QA targets.