research

A research workflow that turns sources such as web pages, PDFs, and GitHub repositories into a structured knowledge base. It can refresh that knowledge when sources change.

In plain words
What is it for?
Use it to process online sources, PDF documents, or GitHub repositories and update the resulting knowledge base later.
Why use it?
It gives research a reusable structure instead of leaving findings scattered across separate reading sessions.

Plugin for Claude Code

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.

Claude Code
/plugin marketplace add harnessprotocol/harness-kit
agentmods
npx agentmods add plugins/harnessprotocol/harness-kit/research
Clone the repo
git clone --depth 1 https://github.com/harnessprotocol/harness-kit

Made for: Claude Code.

Per session not measured What this adds to a session before it is invoked.
When invoked not measured Not applicable: nothing here is loaded into a session.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Security

Grade A, and why

research 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 yesterday.

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/.claude-plugin/plugin.json · 20 lines

What it actually says

{
  "name": "research",
  "description": "Process any source into a structured, compounding knowledge base with refresh capability",
  "version": "0.5.1",
  "category": "research-knowledge",
  "tags": ["research", "knowledge-base", "web-scraping", "pdf", "github", "sources"],
  "skills": ["research", "refresh-research"],
  "requires": {
    "env": [
      {
        "name": "GH_TOKEN",
        "description": "GitHub personal access token — used by gh CLI for repository content fetching",
        "required": false,
        "sensitive": true,
        "when": "Processing GitHub repository URLs"
      }
    ]
  }
}
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. yesterday First seen · 20 lines scan A d81c530c1f3f

Subscribe to this mod's changes

research is a plugin published in the GitHub repository harnessprotocol/harness-kit (10 stars, last pushed 2d ago), licensed Apache-2.0. Its token cost is not measured: this kind of file is read by the harness, not the model. 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.