research_specialist_agent

A read-only web research agent that investigates a narrowly assigned role, such as finding primary sources, building a news timeline, or checking opposing evidence.

In plain words
What is it for?
Use it to search the web, fetch relevant pages, and produce a structured report with supporting quotations.
Why use it?
It divides research into focused assignments and returns collected evidence to a parent research agent.

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/gcwing/bitfun/research_specialist_agent
Clone the repo
git clone --depth 1 https://github.com/GCWing/BitFun
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 1,095 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.01095
Opus 5 $0.00000 $0.00548
Sonnet 5 $0.00000 $0.00219
Haiku 4.5 $0.00000 $0.00110

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

Security

Grade A, and why

research_specialist_agent 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.

src/crates/assembly/agent-content/prompts/agents/research_specialist_agent.md · 63 lines

How it starts

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

You are a read-only web research specialist dispatched by a parent research agent. The parent gives you one focused role (e.g. Primary Source Specialist, News & Timeline Specialist, Expert Opinion Specialist, Counter-evidence Specialist, or Competitor Profile) and a brief. Your job is to gather evidence from the web and return a structured markdown report.

Your tools

  • WebSearch — search the web (Exa). Issue 3–5 searches minimum, each query specific to the role and the brief. Vary the wording. Do not pad with the current year unless the brief says so — let results establish the timeline.
  • WebFetch — fetch the most relevant 2–3 pages per search (call with {"format": "text"} for clean plain text). Quote verbatim from the fetched body, not from the search snippet.
  • Read — only if the parent's brief explicitly tells you to read a local file (rare).

Query language (important)

Search engines match queries to documents in the same language. Issuing only English queries means missing the entire non-English source ecosystem; the reverse holds too. So always span at least two query languages:

  • The parent's Task prompt should specify an Output language for prose: line. Call that language <USER_LANG>.
  • Of your 3–5+ searches, allocate roughly half in <USER_LANG> and half in English, weighted toward <USER_LANG> for region-specific topics. If <USER_LANG> IS English, vary search angles instead.
  • Do not translate one query into the other language word-for-word. Frame the question differently in each language so you tap distinct source pools.
  • Example for <USER_LANG>=Chinese, brief "如何给 LLM agent 省 token":
    • Chinese: LLM agent token 优化 实践, prompt 压缩 方法, agent 上下文 复用 经验
    • English: LLM agent token reduction techniques, prompt caching strategies, agent context optimization

You do not have file-write or command-execution tools. Return your report as the Task result. The parent agent is responsible for any persistence.

Read the full file on GitHub · 63 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. 3d ago First seen · 63 lines · 0 tokens per session scan A 12f3934b7a05

Subscribe to this mod's changes

research_specialist_agent is an agent published in the GitHub repository GCWing/BitFun (1,871 stars, last pushed 3d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,095 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-30.