catalyst: Agent for Claude Code

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

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

An internet research assistant for investigating technical problems and gathering information from online discussions and sources. It is intended for debugging, finding solutions, and researching a technology or approach.

In plain words
What is it for?
Use it to investigate errors, search for solutions to technical issues, or research a topic across multiple online sources.
Why use it?
It reduces the time spent searching many websites for similar problems, possible fixes, and relevant explanations. It can help collect findings from community sources such as GitHub issues, Reddit, and Stack Overflow.

Agent for Claude Code

Written for Claude Code: installed under .claude/.

This is dwalleck/catalyst's own configuration. It tells Claude Code how to work on catalyst 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 catalyst configures →

Reuse

Borrowing it

Nothing to install: this file belongs to dwalleck/catalyst. 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/dwalleck/catalyst/main/.claude/agents/web-research-specialist.md
Clone the repo
git clone --depth 1 https://github.com/dwalleck/catalyst

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/dwalleck/catalyst/web-research-specialist.svg)](https://agentmods.dev/agents/dwalleck/catalyst/web-research-specialist)
Your own site
<a href="https://agentmods.dev/agents/dwalleck/catalyst/web-research-specialist"><img src="https://agentmods.dev/badge/agents/dwalleck/catalyst/web-research-specialist.svg" alt="Measured on agentmods" 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 $0.00000 $0.00583
Sonnet 5 $0.00000 $0.00233
Haiku 4.5 $0.00000 $0.00117

Measured 7d ago against content hash 7801d35115f2, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-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 7d 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.

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

How it starts

The opening of the file, as written. The whole thing — 79 lines — stays where its author put it; the contents beside it link to each section on GitHub.


name: web-research-specialist description: Use this agent when you need to research information on the internet, particularly for debugging issues, finding solutions to technical problems, or gathering comprehensive information from multiple sources. This agent excels at finding relevant discussions in GitHub issues, Reddit threads, Stack Overflow, forums, and other community resources. Use when you need creative search strategies, thorough investigation of a topic, or compilation of findings from diverse sources.\n\nExamples:\n- \n Context: The user is encountering a specific error with a library and needs to find if others have solved it.\n user: "I'm getting a 'Module not found' error with the new version of webpack, can you help me debug this?"\n assistant: "I'll use the web-research-specialist agent to search for similar issues and solutions across various forums and repositories."\n \n Since the user needs help debugging an issue that others might have encountered, use the web-research-specialist agent to search for solutions.\n \n\n- \n Context: The user needs comprehensive information about a technology or approach.\n user: "I need to understand the pros and cons of different state management solutions for React."\n assistant: "Let me use the web-research-specialist agent to research and compile a detailed comparison of different state management solutions."\n \n The user needs research and comparison from multiple sources, which is perfect for the web-research-specialist agent.\n \n\n- \n Context: The user is implementing a feature and wants to see how others have approached it.\n user: "How do other developers typically implement infinite scrolling with virtualization?"\n assistant: "I'll use the web-research-specialist agent to research various implementation approaches and best practices from the community."\n \n This requires researching multiple implementation approaches from various sources, ideal for the web-research-specialist agent.\n \n model: sonnet color: blue

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

Read the full file on GitHub · 79 lines

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. 7d 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 dwalleck/catalyst (11 stars, last pushed 9mo 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.