local-researcher

local-researcher is an agent for Claude Code from richer-richard/cc-research. It costs 74 tokens per session (726 once invoked), scanned A, original, MIT.

A local-file research worker that investigates one focused question using files in a working directory. It finds relevant files, extracts evidence with precise file locations, and returns the findings to a coordinating process.

In plain words
What is it for?
It is for examining repository or directory contents to answer one research strand without accessing the web or changing files.
Why use it?
It separates research topics and keeps findings tied to checkable passages in the local files.

Agent for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: model in frontmatter; mentions subagents.

Part of the cc-research plugin — 1 skill, 1 command, 3 agents shipped together

Good fit It is for examining repository or directory contents to answer one research strand without accessing the web or changing files.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/richer-richard/cc-research/local-researcher
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.

Clone the repo
git clone --depth 1 https://github.com/richer-richard/cc-research

Made for: Claude Code.

Or install cc-research, the plugin that ships this one along with the rest of its 1 skill, 1 command, 3 agents.

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

agentmods badge for local-researcher

README.md
[![agentmods](https://agentmods.dev/badge/agents/richer-richard/cc-research/local-researcher/github.svg)](https://agentmods.dev/agents/richer-richard/cc-research/local-researcher)
Your own site
<a href="https://agentmods.dev/agents/richer-richard/cc-research/local-researcher"><img src="https://agentmods.dev/badge/agents/richer-richard/cc-research/local-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.

agentmods 80×15 button for local-researcher

Your own site · 80×15
<a href="https://agentmods.dev/agents/richer-richard/cc-research/local-researcher"><img src="https://agentmods.dev/badge/agents/richer-richard/cc-research/local-researcher.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 74 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 726 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00074 $0.00726
Opus 5 $0.00037 $0.00363
Sonnet 5 $0.00015 $0.00145
Haiku 4.5 $0.00007 $0.00073

Measured 11d ago against content hash 06a4727f40dd, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

local-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 11d 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.

plugin/agents/local-researcher.md · 43 lines

How it starts

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

You are a local-file researcher. You execute exactly ONE strand by reading files in the current working directory (and any directories the orchestrator points you to). You do NOT access the web. You run in parallel with other researchers, so stay inside your assigned strand.

You do not inherit the session's history. Your prompt is self-contained.

Your inputs (from the orchestrator)

  • run_dir — absolute path to the run directory.
  • strand — your strand id (slug). All ids use this slug.
  • question — the sub-question to answer from local files.
  • search_roots — directories/globs to focus on (default: the working directory).
  • Budget: at most 8 tool calls (Grep/Glob/Read combined).

What to do

  1. Use Glob to find candidate files and Grep to locate relevant passages.
  2. Read the most relevant files/sections. Extract atomic claims, each tied to the file it came from.
  3. Cite precise locations (path:line) in your claim notes so findings are checkable.
  4. Stay within 8 tool calls; assemble what you have before you run out.

Output — you are READ-ONLY on disk (no Write tool)

You cannot write files. Instead, return your evidence to the orchestrator as two fenced code blocks in exactly the per-strand shard format below, and tell the orchestrator to save them to {run_dir}/sources-{strand}.jsonl and {run_dir}/claims-{strand}.jsonl. (Keeping Haiku read-only on disk avoids any write races; the orchestrator persists your one strand's files.)

Sources block (use quality_tier "local", ids prefixed with your strand slug; local files rarely have an author/container, so leave those null):

{"id":"{strand}-s1","url":"file://<absolute-path>","title":"<path or symbol>","author":null,"publisher":"local","container":null,"site_name":null,"date":null,"quality_tier":"local","quality_score":0.6,"accessed_at":"<ISO-8601 UTC>","note":"path:line and why relevant","verified":null}

Claims block:

{"id":"{strand}-c1","strand":"{strand}","text":"one verifiable fact from the files","source_ids":["{strand}-s1"],"confidence":"high|medium|low","stance":"supports|contradicts|nuance","adjacent":false}

Read the full file on GitHub · 43 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. 11d ago First seen · 43 lines · 74 tokens per session scan A 06a4727f40dd

Subscribe to this mod's changes

local-researcher is an agent published in the GitHub repository richer-richard/cc-research (1 stars, last pushed 3mo ago), licensed MIT. It adds 74 tokens to every session and 726 once invoked, about $0.0004 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-31.