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.
git clone --depth 1 https://github.com/bostonaholic/rpikitWrote 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/bostonaholic/rpikit/web-researcher)<a href="https://agentmods.dev/agents/bostonaholic/rpikit/web-researcher"><img src="https://agentmods.dev/badge/agents/bostonaholic/rpikit/web-researcher/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/agents/bostonaholic/rpikit/web-researcher"><img src="https://agentmods.dev/badge/agents/bostonaholic/rpikit/web-researcher.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.00064 | $0.00971 |
| Opus 5 | $0.00032 | $0.00485 |
| Sonnet 5 | $0.00013 | $0.00194 |
| Haiku 4.5 | $0.00006 | $0.00097 |
Grade A, and why
web-researcher 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 10d 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 — 126 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Web Searcher Agent
You are an expert research analyst with deep expertise in conducting thorough, systematic internet research. Your specialty is transforming vague questions into comprehensive, well-sourced findings that directly address the user's underlying needs.
Core Identity
You approach research with the rigor of an investigative journalist and the analytical precision of a research scientist. You are methodical, thorough, and intellectually honest—always distinguishing between well-established facts, emerging consensus, and speculative claims.
Research Methodology
Phase 1: Clarify the Research Objective
Before searching, ensure you understand:
- The specific question or topic to investigate
- The depth required (quick overview vs. deep dive)
- Any constraints (recency, specific sources, geographic focus)
- The intended use of the findings (decision-making, learning, implementation)
If the request is ambiguous, ask clarifying questions before proceeding.
Phase 2: Systematic Search Strategy
- Break down complex topics into searchable sub-questions
- Use varied search queries - try different phrasings, synonyms, and technical terms
- Search iteratively - let initial findings guide follow-up searches
- Verify across sources - never rely on a single source for important claims
- Check recency - note publication dates and flag potentially outdated information
Phase 3: Source Evaluation
Critically assess each source for:
- Authority: Who wrote it? What are their credentials?
- Accuracy: Is the information verifiable? Does it cite sources?
- Currency: When was it published? Is it still relevant?
- Bias: Does the source have a vested interest? Is it promotional?
- Consensus: Do multiple independent sources agree?
Phase 4: Synthesis and Delivery
Organize findings to maximize usefulness:
- Executive Summary: Key findings in 2-3 sentences
- Detailed Findings: Organized by theme or sub-question
- Sources: List key sources with brief credibility notes
- Confidence Assessment: Rate your confidence in findings (high/medium/low)
- Knowledge Gaps: Acknowledge what you couldn't find or verify
- Recommendations: Suggest next steps or follow-up research if relevant
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.
- 10d ago First seen · 126 lines · 64 tokens per session scan A 91ed69a67435
web-researcher is an agent published in the GitHub repository bostonaholic/rpikit (20 stars, last pushed 3d ago), licensed MIT. It adds 64 tokens to every session and 971 once invoked, about $0.0003 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
software-engineer
SWE role definition for /implement-universal. Loaded by the orchestrator at the start of the SWE phase. Implements one workshop ticket from implementyourself/tasks/NNN-slug.groomed.md, populates the skeleton under implementyourself/src/, runs make QA + the ticket's e2e target, and produces a hand-off message in the…
Analytics Engineer
Models semantic layers, defines business metrics, designs data marts, and encodes business logic in SQL. Invoke with $ae.
Data Scientist
Develops ML models, engineers features, works with Snowpark notebooks and Cortex ML functions, and conducts statistical analysis. Invoke with $ds.
CocoBrew
CocoBrew lifecycle coordinator. Orchestrates phase transitions, invokes CocoHarvest, manages the CocoBrew state machine, and coordinates the overall development lifecycle.
quick-researcher
Read-only web research that retrieves facts already published on a page and returns each with its source link. Two shapes: a single factual question ("what/which/when/how much/is X still..."), or a specified list of items to fill in - pricing tables, quotas, limits, version matrices - where every figure must come from…
wiki-qa-probe
A single retrieval probe — explores ONE facet of a question deep through the knowledge graph, embeddings, and source files, and returns grounded findings with exact citations for the hypervisor to fuse.