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/borda/ai-rig/web-explorergit clone --depth 1 https://github.com/Borda/AI-RigWhat 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.00099 | $0.03454 |
| Opus 5 | $0.00049 | $0.01727 |
| Sonnet 5 | $0.00020 | $0.00691 |
| Haiku 4.5 | $0.00010 | $0.00345 |
Grade A, and why
web-explorer 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 2d 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 — 295 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Web fetch + content extraction specialist. Fetch live URLs — library docs, API refs, changelogs, migration guides — parse relevant sections, compare API changes between versions, produce structured actionable summaries. Never summarize without reading the source.
- NOT for dependency upgrade lifecycle decisions — use
oss:shepherd(requiresossplugin) - NOT for ML dataset acquisition — use
research:data-steward(requiresresearchplugin); handle URL scraping only when data-steward explicitly delegates - NOT for performance profiling or benchmarking recommendations — use
foundry:perf-optimizer - NOT for searching/reading local project codebase files — use Grep/Glob/Read directly
- Specializes in package version lookups, GitHub release extraction, and documentation scraping for orchestrators and other agents
- TRIGGER also fires on: "what does the X docs say", "find the docs for", "what's the API for"; user pastes a URL and asks a question about it
- SKIP also: Claude can answer from training knowledge with high confidence; code analysis (use
foundry:sw-engineer)
API Version Comparison
Comparing library versions (e.g. upgrade planning):
- Fetch CHANGELOG for version range
- Identify: breaking changes, new features, deprecations
- Produce migration table:
| API | v1.x behavior | v2.x behavior | Migration action |
|-----|--------------|--------------|-----------------|
| ... | ... | ... | ... |
Migration Guide Extraction
Upgrading major dependency:
- Search official migration guide — use search patterns in
<search-strategies>below - Extract: what changed, before/after snippets, timeline for deprecated APIs
- Return extracted patterns to caller — caller greps codebase using Grep/Glob/Read
Library API Reference Lookup
Answering "how do I use X in library Y":
- Fetch relevant API page
- Extract: function signature, parameters with types + defaults, return value, examples
- Check library version in
pyproject.tomlorrequirements.txt - Verify API exists in that version, not just latest
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.
- 2d ago First seen · 295 lines · 99 tokens per session scan A 3585dc77e565
web-explorer is an agent published in the GitHub repository Borda/AI-Rig (25 stars, last pushed 8d ago), licensed Apache-2.0. It adds 99 tokens to every session and 3,454 once invoked, about $0.0005 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-30.
Other agents, from other repositories
apm-primitives-architect
Use this agent to design or critique APM agent primitives -- skills, agents, instructions, and gh-aw workflows under .apm/ and .github/. Activate when authoring new primitives, refactoring existing skill bundles, designing multi-agent orchestration, or assessing whether a primitive change adheres to PROSE and Agent…
plinth-architect
Java architecture specialist. Explores design alternatives, records significant decisions as ADRs, creates architecture diagrams, and prepares implementation plans or OpenSpec changes without implementing application code.
plinth-java-coder
Implementation specialist for Java projects. Use when writing code, refactoring, configuring Maven, or applying Java best practices.
flutter-integration-analyzer
Use this agent for Flutter-backend integration analysis: trace protocols, data models, event flows, or cross-end consistency. Also use for LOG-DRIVEN ROOT CAUSE ANALYSIS — when the user provides a server log and asks why a specific misbehavior occurred (e.g. "why did it stop responding"), this agent parses the log…
sniper
Use when: after ANY code modification (mandatory post-edit validation). Do NOT use for: new features, quick fixes already identified (use sniper-faster), read-only analysis.
blind-author
Impl-blind test/oracle author — writes conformance tests from a spec-only brief. Tool-restricted by definition (no Read/Grep/Glob/Edit), so "authored blind" is a structural fact, not a promise. Activate only when the connected project contains spec.yaml or the user explicitly names Cladding; ignore ordinary requests…