stage-cli: Agent for Claude Code

.agents/agents/web-research-specialist.md

web-research-specialist is an agent for Claude Code from ReviewStage/stage-cli. It costs 0 tokens per session (1,165 once invoked), scanned A, a copy of web-research-specialist, MIT.

A web-research specialist is an AI helper for investigating technical questions across sources such as GitHub issues, Reddit, Stack Overflow, forums, and repositories.

In plain words
What is it for?
It helps find solutions to technical problems, investigate bugs, and gather information about a technology from multiple online sources.
Why use it?
It reduces the time spent searching scattered discussions when debugging an error or comparing approaches.

Agent for Claude Code

Written for Claude Code: a Claude Code subagent (agents/*.md). Also seen: model in frontmatter; installed under .agents/ (shared by several agents).

This is ReviewStage/stage-cli's own configuration. It tells Claude Code how to work on stage-cli itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything stage-cli configures →

Reuse

Borrowing it

Nothing to install: this file belongs to ReviewStage/stage-cli. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/ReviewStage/stage-cli/main/.agents/agents/web-research-specialist.md
Clone the repo
git clone --depth 1 https://github.com/ReviewStage/stage-cli

Made for: Claude Code.

Wrote 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.

agentmods badge for web-research-specialist

README.md
[![agentmods](https://agentmods.dev/badge/agents/reviewstage/stage-cli/web-research-specialist/github.svg)](https://agentmods.dev/agents/reviewstage/stage-cli/web-research-specialist)
Your own site
<a href="https://agentmods.dev/agents/reviewstage/stage-cli/web-research-specialist"><img src="https://agentmods.dev/badge/agents/reviewstage/stage-cli/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.

agentmods 80×15 button for web-research-specialist

Your own site · 80×15
<a href="https://agentmods.dev/agents/reviewstage/stage-cli/web-research-specialist"><img src="https://agentmods.dev/badge/agents/reviewstage/stage-cli/web-research-specialist.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,165 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin 100% copy Near-identical to another mod in the catalogue.
Token cost

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.

ModelPer sessionOnce 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

Measured 1mo ago against content hash 7801d35115f2, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 1mo 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.

Origin

This is a copy

100% identical to web-research-specialist — 0 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.

.agents/agents/web-research-specialist.md · 79 lines

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:

  1. 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
  2. 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
  3. 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
  4. 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:

  1. Executive Summary (key findings in 2-3 sentences)
  2. Detailed Findings (organized by relevance/approach)
  3. Sources and References (with direct links)
  4. Recommendations (if applicable)
  5. 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.

Changes

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.

  1. 1mo ago First seen · 79 lines · 0 tokens per session scan A 7801d35115f2

Subscribe to this mod's changes

web-research-specialist is an agent published in the GitHub repository ReviewStage/stage-cli (274 stars, last pushed 1mo ago), licensed MIT. 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 0 lines, and is treated as a copy.