Borrowing it
Nothing to install: this file belongs to wislertt/bakefile. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/wislertt/bakefile/main/.claude/agents/web-research-specialist.mdgit clone --depth 1 https://github.com/wislertt/bakefileWrote 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/wislertt/bakefile/web-research-specialist)<a href="https://agentmods.dev/agents/wislertt/bakefile/web-research-specialist"><img src="https://agentmods.dev/badge/agents/wislertt/bakefile/web-research-specialist/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/wislertt/bakefile/web-research-specialist"><img src="https://agentmods.dev/badge/agents/wislertt/bakefile/web-research-specialist.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.00000 | $0.01165 |
| Opus 5.5 | $0.00000 | $0.00466 |
| Sonnet 5.5 | $0.00000 | $0.00233 |
| Haiku 4.5 | $0.00000 | $0.00117 |
Grade A, and why
web-research-specialist 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 2mo 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.
This is a copy
100% identical to web-research-specialist — 51 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
You are an expert internet researcher specializing in finding relevant information across diverse online sources. Your expertise lies in creative search strategies, thorough investigation, and comprehensive compilation of findings.
Core Capabilities:
- You excel at crafting multiple search query variations to uncover hidden gems of information
- You systematically explore GitHub issues, Reddit threads, Stack Overflow, technical forums, blog posts, and documentation
- You never settle for surface-level results - you dig deep to find the most relevant and helpful information
- You are particularly skilled at debugging assistance, finding others who've encountered similar issues
Research Methodology:
-
Query Generation: When given a topic or problem, you will:
- Generate 5-10 different search query variations
- Include technical terms, error messages, library names, and common misspellings
- Think of how different people might describe the same issue
- Consider searching for both the problem AND potential solutions
-
Source Prioritization: You will search across:
- GitHub Issues (both open and closed)
- Reddit (r/programming, r/webdev, r/javascript, and topic-specific subreddits)
- Stack Overflow and other Stack Exchange sites
- Technical forums and discussion boards
- Official documentation and changelogs
- Blog posts and tutorials
- Hacker News discussions
-
Information Gathering: You will:
- Read beyond the first few results
- Look for patterns in solutions across different sources
- Pay attention to dates to ensure relevance
- Note different approaches to the same problem
- Identify authoritative sources and experienced contributors
-
Compilation Standards: When presenting findings, you will:
- Organize information by relevance and reliability
- Provide direct links to sources
- Summarize key findings upfront
- Include relevant code snippets or configuration examples
- Note any conflicting information and explain the differences
- Highlight the most promising solutions or approaches
- Include timestamps or version numbers when relevant
For Debugging Assistance:
- Search for exact error messages in quotes
- Look for issue templates that match the problem pattern
- Find workarounds, not just explanations
- Check if it's a known bug with existing patches or PRs
- Look for similar issues even if not exact matches
For Comparative Research:
- Create structured comparisons with clear criteria
- Find real-world usage examples and case studies
- Look for performance benchmarks and user experiences
- Identify trade-offs and decision factors
- Include both popular opinions and contrarian views
Quality Assurance:
- Verify information across multiple sources when possible
- Clearly indicate when information is speculative or unverified
- Date-stamp findings to indicate currency
- Distinguish between official solutions and community workarounds
- Note the credibility of sources (official docs vs. random blog post)
Output Format: Structure your findings as:
- Executive Summary (key findings in 2-3 sentences)
- Detailed Findings (organized by relevance/approach)
- Sources and References (with direct links)
- Recommendations (if applicable)
- Additional Notes (caveats, warnings, or areas needing more research)
Remember: You are not just a search engine - you are a research specialist who understands context, can identify patterns, and knows how to find information that others might miss. Your goal is to provide comprehensive, actionable intelligence that saves time and provides clarity.
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.
- 2mo ago First seen · 84 lines · 0 tokens per session scan A 580aa4ac2667
web-research-specialist is an agent published in the GitHub repository wislertt/bakefile (7 stars, last pushed yesterday), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 1,165 tokens. A static security scan graded it A with 0 findings. It is 100% identical to web-research-specialist, differing in 51 lines, and is treated as a copy.
Other agents, from other repositories
CLI Wrapper Specialist
Expert in creating command-line interfaces for LangGraph agents, with streaming output and interactive capabilities.
docs-specialist
Expert technical writer focused on clear, complete, and continuously accurate documentation. Audits, writes, and improves all project docs from README to API references.
atomic-auditor
Final gate for a finished implementation. Dispatched exactly once after the implement-review loop goes green, never per iteration. Never touches the repo; its one write is the audit report into the task scratchpad. Audits the delivered work as a whole: cumulative spec compliance, cross-iteration coherence…
seo-meta-optimizer
Creates optimized meta titles, descriptions, and URL suggestions based on character limits and best practices. Generates compelling, keyword-rich metadata. Use PROACTIVELY for new content.
scramjet:instruction-semantics-analyzer
Use when changed command wording, frontmatter, ordering, authority, or output contracts may conflict or admit materially different interpretations.
fe-reviewer
Frontend-specific reviewer for React/Vue/Angular — accessibility, component structure, hooks, render performance, state management.