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/blencorp/claude-code-kitWrote 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/blencorp/claude-code-kit/web-research-specialist)<a href="https://agentmods.dev/agents/blencorp/claude-code-kit/web-research-specialist"><img src="https://agentmods.dev/badge/agents/blencorp/claude-code-kit/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/blencorp/claude-code-kit/web-research-specialist"><img src="https://agentmods.dev/badge/agents/blencorp/claude-code-kit/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.00042 | $0.00777 |
| Opus 5.5 | $0.00017 | $0.00311 |
| Sonnet 5.5 | $0.00008 | $0.00155 |
| Haiku 4.5 | $0.00004 | $0.00078 |
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.
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.
- 1mo ago First seen · 80 lines · 42 tokens per session scan A fd90da6e3458
web-research-specialist is an agent published in the GitHub repository blencorp/claude-code-kit (107 stars, last pushed 10mo ago), licensed MIT. It adds 42 tokens to every session and 777 once invoked, about $0.0002 per session on Opus 5.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
debugger
Diagnoses and fixes failed modules using root-cause analysis, not guessing.
loom-advisor
Read-only advisory agent for debugging and repeated failures. Spawned instead of a blind retry when an implementer has failed twice on the same task, or a bug resists straightforward diagnosis. Returns a root-cause diagnosis plus one concrete next step.
debugger
Investigate errors systematically to find root cause before attempting fixes. Gathers evidence, analyzes patterns, and forms testable hypotheses.
evolve-retrospective
Failure post-mortem agent for the Evolve Loop. Fires only on Auditor FAIL or WARN verdicts. Reads cycle artifacts and produces a structured retrospective + failure-lesson YAML files. READ-ONLY outside the lessons directory.
type-reconstructor
Dedicated struct/class reconstruction from IDA Pro decompiled binaries. Scans every function for memory access patterns, merges evidence across the module, resolves vtable and COM interface layouts, and generates compilable C++ header files with per-field confidence annotations. Use for full-module or single-class…
runtime-observer
Dynamic observation agent designed to inspect running applications, trace state transitions, log API traffic, and flag race conditions, cache states, or timing issues. Trigger with "start runtime observer", "observe live system", "trace API calls", or during characterization test validation.