research-fetcher

research-fetcher is an agent for Claude Code from harnessprotocol/harness-kit. It costs 33 tokens per session (360 once invoked), scanned A, original, Apache-2.0.

A background agent that retrieves content from given web addresses, saves the unprocessed results, and checks that the saved files are not empty. It does not summarize or interpret the content.

In plain words
What is it for?
Use it to fetch explicitly provided URLs, save their raw contents to a specified path, and confirm that the output was written.
Why use it?
It separates fetching source material from later analysis, preserving the original fetched text for verification. This helps other workflows use reliable raw inputs.

Agent for Claude Code

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

Part of the research plugin — 2 skills, 1 agent shipped together

Good fit Use it to fetch explicitly provided URLs, save their raw contents to a specified path, and confirm that the output was written.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/harnessprotocol/harness-kit/research-fetcher
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/harnessprotocol/harness-kit

Made for: Claude Code.

Or install research, the plugin that ships this one along with the rest of its 2 skills, 1 agent.

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 research-fetcher

README.md
[![agentmods](https://agentmods.dev/badge/agents/harnessprotocol/harness-kit/research-fetcher/github.svg)](https://agentmods.dev/agents/harnessprotocol/harness-kit/research-fetcher)
Your own site
<a href="https://agentmods.dev/agents/harnessprotocol/harness-kit/research-fetcher"><img src="https://agentmods.dev/badge/agents/harnessprotocol/harness-kit/research-fetcher/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 research-fetcher

Your own site · 80×15
<a href="https://agentmods.dev/agents/harnessprotocol/harness-kit/research-fetcher"><img src="https://agentmods.dev/badge/agents/harnessprotocol/harness-kit/research-fetcher.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 33 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 360 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.00033 $0.00360
Opus 5.5 $0.00013 $0.00144
Sonnet 5.5 $0.00007 $0.00072
Haiku 4.5 $0.00003 $0.00036

Measured 1mo ago against content hash 7c3af0bc9b4f, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

research-fetcher 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 1mo 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.

plugins/research/agents/research-fetcher.md · 54 lines

What it actually says

You are a focused content fetcher. Your job is to fetch content from sources and save raw output — not to analyze, summarize, or synthesize.

What you do

  • Fetch content from URLs (WebFetch)
  • Save raw content to files (Write)
  • Run shell commands to check file existence and content length (Bash: ls, wc, cat)
  • Read existing files to avoid re-fetching (Read)

Workflow (follow in order)

Step 1: Fetch the source

Use WebFetch to retrieve content from the target URL. If fetch fails, note the error and stop — do not retry more than once.

Step 2: Save raw content

Write the fetched content to the output path provided. Use the exact filename specified. Do not transform, summarize, or truncate content.

Step 3: Verify the file

Check that the file was written and has non-zero size:

ls -lh <output-path>
wc -c <output-path>

Report the file path and line count.

What you never do

  • Summarize or analyze content — just fetch and save
  • Choose output filenames unless explicitly given one
  • Fetch content that wasn't explicitly requested
  • Write to paths outside the directory you were given

Output

When complete, report:

  • Source URL fetched
  • Output file path
  • File size / line count
  • Any errors encountered
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. 1mo ago First seen · 54 lines · 33 tokens per session scan A 7c3af0bc9b4f

Subscribe to this mod's changes

research-fetcher is an agent published in the GitHub repository harnessprotocol/harness-kit (10 stars, last pushed today), licensed Apache-2.0. It adds 33 tokens to every session and 360 once invoked, about $0.0001 per session on Opus 5.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.

Related

Other agents, from other repositories

webapi-integration

Use this agent when the user needs to integrate Power Pages Web API for a specific Dataverse table into their frontend code. Trigger examples: "integrate web api for products table", "add api calls for orders", "connect my site to the blog posts table", "implement crud for categories", "set up web api client", "create…

microsoft/power-platform-skills · 182 tokens

genpage-edit-planner

Plans edits to an existing generative page. Reads the downloaded page artifacts (source, original prompt, config), analyzes the current implementation against the user's edit intent, and returns a proposed edit plan for the orchestrator to present for approval. Writes genpage-edit-plan.md, for the orchestrator to…

microsoft/power-platform-skills · 141 tokens

canvas-create-screens

Groups approved functional intent into task-oriented screens, in-screen states and navigation without choosing Canvas controls.

microsoft/power-platform-skills · 24 tokens

otp-advisor

OTP patterns specialist - GenServer, Supervisor, Agent, Task, Registry, ETS. Use proactively when deciding if you need OTP abstractions or simpler solutions.

oliver-kriska/claude-elixir-phoenix · 35 tokens

elixir-way-architect

Synthesizes rewrite analysis and the ADR-000 compatibility bar into an idiomatic Elixir architecture, a complete mechanism ledger, ADRs and divergences. Use when /rewrite:architect has analysis and an accepted bar.

oliver-kriska/claude-elixir-phoenix · 50 tokens

plan-creation-eng-lead

Engineering and Delivery Lead for implementation planning. Produces work breakdown structures, effort estimates, dependency graphs, milestones, parallel opportunities, and risk registers. Use when you need structured delivery planning for any implementation topic.

QBall-Inc/the-bulwark · 48 tokens