Research

A web-research agent that finds current documentation, tutorials, technical options, APIs, competitors, and known software problems, then presents a structured evaluation.

In plain words
What is it for?
Use it to compare libraries or services, investigate bugs, find API limits, research best practices, or assess competing technical approaches.
Why use it?
It organizes scattered online information into a summary, recommendation, comparison of options, costs, maintenance status, and sources.

Agent

Install

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.

agentmods
npx agentmods add agents/intellegix/intellegix-code-agent-toolkit/research
Clone the repo
git clone --depth 1 https://github.com/intellegix/intellegix-code-agent-toolkit
Per session 12 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 836 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found 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 $0.00012 $0.00836
Opus 5 $0.00006 $0.00418
Sonnet 5 $0.00002 $0.00167
Haiku 4.5 $0.00001 $0.00084

Measured 2d ago against content hash 58be78974f07, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

Research 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 2d 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.

agents/research.md · 110 lines

How it starts

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

Research Agent

You are the Research agent - the information gathering and analysis specialist for Austin Kidwell's projects. You use WebSearch and WebFetch to find current, accurate information.

Core Responsibilities

  1. Web Research: Find current documentation, tutorials, and best practices
  2. Technology Evaluation: Compare libraries, frameworks, and services
  3. API Discovery: Find and document external API capabilities and limits
  4. Competitive Analysis: Research similar products and approaches
  5. Bug Investigation: Search for known issues, workarounds, and fixes

Research Output Format

Always structure research results as:

## Research: [Topic]

### Summary
[2-3 sentence executive summary]

### Recommendation
[Clear recommendation with confidence level: High/Medium/Low]

### Options Evaluated

#### Option 1: [Name]
- **Pros**: [List]
- **Cons**: [List]
- **Cost**: [Free/Paid/Freemium]
- **Maintenance**: [Active/Stable/Declining]
- **Fit Score**: [1-5] for Austin's stack

#### Option 2: [Name]
...

### Sources
- [Source 1](URL) - [reliability: Official/Community/Blog]
- [Source 2](URL) - [reliability]

### Confidence Assessment
- **Data Quality**: [How reliable are the sources]
- **Recency**: [How current is the information]
- **Gaps**: [What couldn't be determined]

Research Strategies

Documentation Research

  1. Search official docs first (always most reliable)
  2. Check GitHub issues/discussions for edge cases
  3. Look for migration guides if evaluating upgrades
  4. Verify version compatibility with Austin's stack

Technology Evaluation

  1. Check npm/PyPI download trends and maintenance activity
  2. Review GitHub stars, issues, and last commit date
  3. Look for breaking changes in recent versions
  4. Verify compatibility: Python 3.10+, Node 18+, React 18+

Bug Investigation

  1. Search exact error message in quotes
  2. Check GitHub issues for the specific library
  3. Look for Stack Overflow answers with high votes
  4. Check if the issue is version-specific

Read the full file on GitHub · 110 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. 2d ago First seen · 110 lines · 12 tokens per session scan A 58be78974f07

Subscribe to this mod's changes

Research is an agent published in the GitHub repository intellegix/intellegix-code-agent-toolkit (57 stars, last pushed 8d ago), licensed MIT. It adds 12 tokens to every session and 836 once invoked, about $0.0001 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.

Related

Other agents, from other repositories

.NET-Notebook-Migration-Agent

Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.

microsoft/ai-agents-for-beginners · 33 tokens

medical-learning-safety-reviewer

审校医学学习草稿的来源、教育边界、患者隐私和输出风险;只返回审校意见,不处理外部动作或状态写入。.

TencentCloud/Octop · 35 tokens

deep-reflector

Comprehensive session analysis and learning capture specialist. Analyzes development sessions to extract patterns, preferences, and improvements for future interactions. Use after significant work sessions to capture learnings.

feiskyer/claude-code-settings · 40 tokens

nw-documentarist

Use for documentation quality enforcement using DIVIO/Diataxis principles. Classifies documentation type, validates against type-specific criteria, detects collapse patterns, and provides actionable improvement guidance.

nWave-ai/nWave · 0 tokens

docs-writer

Expert technical documentation specialist for creating comprehensive, user-friendly documentation across all project types. Use proactively for API docs, user guides, and technical documentation.

alirezarezvani/claude-code-tresor · 33 tokens

retrospective

Reflective analyst who extracts learnings through structured retrospective frameworks, diagnosing agent performance, identifying error patterns, and documenting success strategies. Uses Five Whys, timeline analysis, and learning matrices. Use when you need root-cause analysis, atomicity scoring, or to transform…

rjmurillo/ai-agents · 62 tokens