docs-researcher

docs-researcher is an agent for Claude Code from littlebearapps/pitchdocs. It costs 43 tokens per session (1,527 once invoked), scanned A, original, MIT.

An agent that examines a code repository and produces research notes for writing its documentation.

In plain words
What is it for?
Use it to identify a project's hosting platform, inspect its main files and existing documents, and prepare information for a documentation writer.
Why use it?
It gathers project structure, features, platform details, and evidence before documentation is drafted, reducing guesswork.

Agent for Claude Code

Part of the pitchdocs plugin — 16 skills, 15 commands, 4 agents shipped together

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/littlebearapps/pitchdocs/docs-researcher
Clone the repo
git clone --depth 1 https://github.com/littlebearapps/pitchdocs

Made for: Claude Code.

Or install pitchdocs, the plugin that ships this one along with the rest of its 16 skills, 15 commands, 4 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 docs-researcher

README.md
[![agentmods](https://agentmods.dev/badge/agents/littlebearapps/pitchdocs/docs-researcher.svg)](https://agentmods.dev/agents/littlebearapps/pitchdocs/docs-researcher)
Your own site
<a href="https://agentmods.dev/agents/littlebearapps/pitchdocs/docs-researcher"><img src="https://agentmods.dev/badge/agents/littlebearapps/pitchdocs/docs-researcher.svg" alt="Measured on agentmods" height="20"></a>
Per session 43 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,527 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.00043 $0.01527
Opus 5 $0.00022 $0.00763
Sonnet 5 $0.00009 $0.00305
Haiku 4.5 $0.00004 $0.00153

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

Security

Grade A, and why

docs-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 4d 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.

.claude/agents/docs-researcher.md · 173 lines

How it starts

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

Docs Researcher Agent

You are a codebase analyst who extracts everything needed to write compelling documentation. Your job is discovery and extraction — you do not write docs yourself.

Workflow

Step 1: Platform Detection

Detect the hosting platform before any other work:

[ -f ".gitlab-ci.yml" ] && PLATFORM="gitlab"
[ -f "bitbucket-pipelines.yml" ] && PLATFORM="bitbucket"
[ -d ".github" ] && PLATFORM="github"
PLATFORM=${PLATFORM:-$(git remote get-url origin 2>/dev/null | grep -oE '(github|gitlab|bitbucket)' | head -1)}
echo "Platform: ${PLATFORM:-unknown}"

If the platform is not GitHub, load the platform-profiles skill for template paths, badge URLs, and CLI tools.

Step 2: Codebase Discovery

Deeply understand the project:

# Project metadata
cat package.json 2>/dev/null || cat pyproject.toml 2>/dev/null || cat Cargo.toml 2>/dev/null || cat go.mod 2>/dev/null

# Existing docs
cat README.md 2>/dev/null
cat CHANGELOG.md 2>/dev/null
cat CONTRIBUTING.md 2>/dev/null

# Project structure
find . -maxdepth 3 -type f -not -path './.git/*' -not -path './node_modules/*' -not -path './.next/*' -not -path './dist/*' | head -80

# Git history for context
git log --oneline -20 2>/dev/null
git tag --sort=-v:refname | head -10 2>/dev/null

# Key source files
ls src/ 2>/dev/null || ls lib/ 2>/dev/null || ls app/ 2>/dev/null

Classify the project:

PROJECT_TYPE = library | cli | web-app | api | plugin | docs-site | monorepo
LANGUAGE     = typescript | python | go | rust | java | ...
FRAMEWORK    = react | nextjs | fastapi | django | express | cloudflare-workers | ...
AUDIENCE     = developers | devtools | end-users | data-scientists

Detection signals:

  • library: main/exports in package.json, py_modules in pyproject.toml, no bin field
  • cli: bin field in package.json, [project.scripts] in pyproject.toml, cobra/clap imports
  • web-app: next.config, vite.config, app/ directory with routes/pages
  • api: routes/, endpoints/, OpenAPI spec, fastapi/express/hono imports
  • plugin: plugin.json, .claude-plugin/, package.json with claude-code-plugin keyword
  • docs-site: docusaurus.config, mkdocs.yml, astro.config with docs theme
  • monorepo: workspaces in package.json, pnpm-workspace.yaml, lerna.json

Read the full file on GitHub · 173 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. 4d ago First seen · 173 lines · 0 tokens per session scan A 91e03825f9b7

Subscribe to this mod's changes

docs-researcher is an agent published in the GitHub repository littlebearapps/pitchdocs (8 stars, last pushed 3mo ago), licensed MIT. It adds 43 tokens to every session and 1,527 once invoked, about $0.0002 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.

Related

Other agents, from other repositories

data-engineer

Adversarial data and database engineer who assumes the design is mis-normalized and indexed for a workload that does not exist. Audits schemas, migrations, queries, ORM code, document shapes, stream contracts, and pipelines against normalization, dimensional modeling, key-value access patterns, columnar and…

testdouble/han · 216 tokens

on-call-engineer

Adversarial on-call engineer who assumes application source will fail in production and the author will not be paged. Audits application source, not infrastructure, for code-level resilience anti-patterns: missing timeouts, retries without backoff and jitter, non-idempotent operations in retry paths, catch-and-swallow…

testdouble/han · 214 tokens

plan-synthesizer

Synthesizes cross-specialist input into a plan the team can commit to, recording decisions, rejected alternatives with reasons, the evidence behind each call, and the items still open. Reads the inputs from every specialist who contributed, reconciles their recommendations, and applies an evidence standard to each …

testdouble/han · 159 tokens

information-architect

Adversarial information architect who assumes the current documentation is harder to find, orient in, and comprehend than it needs to be. Audits READMEs, API docs, plugin docs, ADR collections, tutorials, and reference content against established IA practice — the four IA systems (organization, labeling, navigation…

testdouble/han · 193 tokens

system-architect

Adversarial system architect who assumes the current cross-service topology is wrong: bounded contexts leak, integrations are synchronously chained where events would decouple, and failure domains are uncontained. Synthesizes boundary-crossing findings into recommendations on bounded-context boundaries, context-map…

testdouble/han · 188 tokens

edge-case-explorer

Systematically discovers and catalogs edge cases that should be covered by tests for a given piece of code. Traces input sources, call chains, and integration boundaries to find boundary values, type coercion traps, external input messiness, state-dependent failures, and error propagation gaps. Use when exploring how…

testdouble/han · 135 tokens