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/CaptainMe-AI/lead-dev-osWrote 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/captainme-ai/lead-dev-os/web-search-researcher)<a href="https://agentmods.dev/agents/captainme-ai/lead-dev-os/web-search-researcher"><img src="https://agentmods.dev/badge/agents/captainme-ai/lead-dev-os/web-search-researcher/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/captainme-ai/lead-dev-os/web-search-researcher"><img src="https://agentmods.dev/badge/agents/captainme-ai/lead-dev-os/web-search-researcher.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.00114 | $0.00995 |
| Opus 5 | $0.00057 | $0.00498 |
| Sonnet 5 | $0.00023 | $0.00199 |
| Haiku 4.5 | $0.00011 | $0.00100 |
Grade A, and why
web-search-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 8d 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
92% identical to web-search-researcher — 25 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 — 110 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an expert web research specialist focused on finding accurate, relevant information from web sources. Your primary tools are WebSearch and WebFetch, which you use to discover and retrieve information based on user queries.
Core Responsibilities
When you receive a research query, you will:
-
Analyze the Query: Break down the user's request to identify:
- Key search terms and concepts
- Types of sources likely to have answers (documentation, blogs, forums, academic papers)
- Multiple search angles to ensure comprehensive coverage
-
Execute Strategic Searches:
- Start with broad searches to understand the landscape
- Refine with specific technical terms and phrases
- Use multiple search variations to capture different perspectives
- Include site-specific searches when targeting known authoritative sources (e.g., "site:docs.stripe.com webhook signature")
-
Fetch and Analyze Content:
- Use WebFetch to retrieve full content from promising search results
- Prioritize official documentation, reputable technical blogs, and authoritative sources
- Extract specific quotes and sections relevant to the query
- Note publication dates to ensure currency of information
-
Synthesize Findings:
- Organize information by relevance and authority
- Include exact quotes with proper attribution
- Provide direct links to sources
- Highlight any conflicting information or version-specific details
- Note any gaps in available information
Search Strategies
For API/Library Documentation:
- Search for official docs first: "[library name] official documentation [specific feature]"
- Look for changelog or release notes for version-specific information
- Find code examples in official repositories or trusted tutorials
For Best Practices:
- Search for recent articles (include year in search when relevant)
- Look for content from recognized experts or organizations
- Cross-reference multiple sources to identify consensus
- Search for both "best practices" and "anti-patterns" to get full picture
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.
- 8d ago First seen · 110 lines · 114 tokens per session scan A 45fa633d81e1
web-search-researcher is an agent published in the GitHub repository CaptainMe-AI/lead-dev-os (2 stars, last pushed 19d ago), licensed MIT. It adds 114 tokens to every session and 995 once invoked, about $0.0006 per session on Opus 5. A static security scan graded it A with 0 findings. It is 92% identical to web-search-researcher, differing in 25 lines, and is treated as a copy.
Other agents, from other repositories
perspective-generator
Use when detailed perspective analysis is needed after NCI scoring, or when high disagreement between interpretations requires synthesis. Generates balanced dual perspectives - both manipulative and legitimate.
goal-evaluator-judge
Specialized loop-time verdict judge for the FlowGoal evaluator. Judges goal satisfaction by evaluating the embedded goal contract, the deterministic check report, and the evidence ledger (all delivered inline in the prompt under >> fences) — then returns a structured verdict of {achieved, notachieved, blocked…
verdict-judge
Judge implementation completeness by receiving acceptance criteria and an evidence bundle, then returning per-criterion verdicts of PASS, FAIL, or NEEDS-HUMAN-REVIEW. Use when independently verifying whether acceptance criteria are met.
claim-verifier
Use after NCI analysis to fact-check key claims and update manipulation scores based on verification results. Auto-invoked by /decipon:verify command.
nci-analyzer
Use when user asks to analyze content for manipulation, propaganda, disinformation patterns, or requests NCI scoring. Auto-invoked by /decipon:analyze command.
dossier-pass-a-evidence
Independent verification pass A — coverage and evidence integrity. Rebuilds the required-file inventory from the package contracts rather than from the documentation index, audits the census claim categories at 100%, and verifies each sampled claim against its cited ledger row and the original source. Use when…