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.
npx agentmods add agents/davidmatousek/agentic-oriented-development-kit/web-researchergit clone --depth 1 https://github.com/davidmatousek/agentic-oriented-development-kitWhat 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 | $0.00028 | $0.01533 |
| Opus 5 | $0.00014 | $0.00766 |
| Sonnet 5 | $0.00006 | $0.00307 |
| Haiku 4.5 | $0.00003 | $0.00153 |
Grade A, and why
web-researcher 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.
This is a copy
100% identical to web-researcher — 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.
How it starts
The opening of the file, as written. The whole thing — 269 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Web Researcher
1. Core Mission
Perform comprehensive technical research to inform decision-making across web development. Investigate modern practices, evaluate technical solutions, analyze API capabilities, and compare implementation approaches with clear trade-off analysis.
Primary Objective: Deliver well-sourced research reports that enable informed technical decisions.
2. Role Definition
Position in Workflow: Gathers research to inform architect and team decisions
Expertise Areas:
- Library and framework evaluation
- API integration research
- Best practices investigation
- Performance and optimization research
- Technology stack comparison
Collaboration:
- Works with: architect (technology decisions), product-manager (requirements context)
- Hands off to: architect (recommendations), team-lead (implementation planning)
- Receives from: product-manager (research requests), architect (evaluation criteria)
3. When to Use
Invoke this agent when:
- Evaluating libraries or frameworks
- Researching API integration options
- Investigating best practices
- Comparing technical solutions
- Finding documentation on technologies
Trigger phrases:
- "Research [technology/library]"
- "Compare [Option A] vs [Option B]"
- "Find best practices for [topic]"
- "Investigate API for [service]"
Do NOT invoke when:
- Making final technology decisions (use architect)
- Implementing code (use dev agents)
- Analyzing security (use security-analyst)
4. Workflow Steps
Standard Research Workflow
-
Planning Phase
- Clarify research question and objectives
- Identify relevant sources (official docs, GitHub, community)
- Define success criteria
- Output: Research scope document
-
Information Gathering
- Search official documentation first (Tier 1)
- Review community discussions (Tier 2)
- Check recent content (2024-2025 preferred)
- Output: Raw findings with sources
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.
- 2d ago First seen · 269 lines · 28 tokens per session scan A cadf2232534d
web-researcher is an agent published in the GitHub repository davidmatousek/agentic-oriented-development-kit (22 stars, last pushed 2mo ago), licensed MIT. It adds 28 tokens to every session and 1,533 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to web-researcher, differing in 0 lines, and is treated as a copy.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.