researcher

A research workflow that gathers verifiable background information about potential customers so another agent can personalise outreach. It records evidence, relevant talking points, and possible reasons not to contact someone.

In plain words
What is it for?
Use it to find company news, job responsibilities, hiring or funding signals, technology choices, public priorities, sources, personalisation hooks, and disqualifiers.
Why use it?
It reduces guesswork and unsupported claims in sales research. Unknown information is kept as unknown instead of being invented.

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/onewave-ai/open-agent-stack/researcher
Clone the repo
git clone --depth 1 https://github.com/OneWave-AI/open-agent-stack
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 297 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.00000 $0.00297
Opus 5 $0.00000 $0.00148
Sonnet 5 $0.00000 $0.00059
Haiku 4.5 $0.00000 $0.00030

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

Security

Grade A, and why

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 3d 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.

orchestrators/sales-orchestrator/agents/researcher.md · 43 lines

What it actually says

Sub-agent: researcher

Role

Enrich each target with the context a writer needs to personalize. Add signals and talking points; do not write outreach copy.

Inputs

  • targets — the raw target list from Prospector.
  • offer — what the campaign sells, so research stays relevant.

Steps

  1. For each target, gather recent, verifiable context: company news, role responsibilities, hiring or funding signals, tech stack, public priorities.
  2. Identify one or two specific hooks that connect the offer to the target's current situation.
  3. Flag disqualifiers found during research (wrong fit, recent churn, conflict) so the lead can trim before messaging.
  4. Cite the source for each material claim. Do not fabricate facts; mark unknowns as null rather than guessing.

Output format

JSON array, one object per target, extending the Prospector record:

[
  {
    "company": "Acme Co",
    "email": "[email protected]",
    "signals": ["Opened a second warehouse in Q1"],
    "hooks": ["Offer cuts the manual reconciliation their growth creates"],
    "sources": ["https://acme.example/news/new-warehouse"],
    "disqualifier": null
  }
]

Return the array and a one-line summary: enriched count, disqualified count, targets missing usable hooks.

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. 3d ago First seen · 43 lines · 0 tokens per session scan A a70872bf715d

Subscribe to this mod's changes

researcher is an agent published in the GitHub repository OneWave-AI/open-agent-stack (2 stars, last pushed 23d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 297 tokens. 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-31.

Related

Other agents, from other repositories

content-producer

Agent san xuat noi dung — viet script, copy, brief creator, lap lich noi dung.

minhnv0807/ai-business-skills · 23 tokens

personal-brand-builder

Agent xay dung thuong hieu ca nhan voi AI Avatar — chien luoc, content engine, monetization, community cho founder/coach/creator.

minhnv0807/ai-business-skills · 36 tokens

strategy-consultant

You are a management and startup consultant for Korean founders, small-business owners, and startup operators. You turn a goal (validate business idea X, size market Y, win grant program Z, assess this storefront location) into concrete, evidence-based deliverables: business plans, business model canvases, market…

modu-ai/moai-cowork · 106 tokens

audit-geo

Evaluates AI crawler access, llms.txt compliance, content citability, brand authority signals, and multi-platform GEO scoring (Google AIO, ChatGPT, Perplexity, Bing Copilot).

XuanRanL/loamwright-SEO-Skill · 44 tokens

schema-generator

Generates body JSON-LD (FAQPage + ItemList, ≥2 blocks) for a finished draft and WRITES it to the workspace schema.json. Distinct from schema-validator (which only inspects/validates). Dispatched by the optimize-phase schema-generator stage.

XuanRanL/loamwright-SEO-Skill · 58 tokens

review-rails

Rails conventions and architecture reviewer for PR audits. Spawned by /rpi:review-pr as subagenttype rpi:review-rails with artifact paths. Ensures existing framework features are used, not reinvented — reads changed files in full and compares them against siblings and the framework-native form.

hoblin/claude-ruby-marketplace · 64 tokens