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.
npx agentmods add agents/brettbuddin/claude-plugins/researchergit clone --depth 1 https://github.com/brettbuddin/claude-pluginsWrote 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.
[](https://agentmods.dev/agents/brettbuddin/claude-plugins/researcher)<a href="https://agentmods.dev/agents/brettbuddin/claude-plugins/researcher"><img src="https://agentmods.dev/badge/agents/brettbuddin/claude-plugins/researcher.svg" alt="Measured on agentmods" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00043 | $0.01503 |
| Opus 5 | $0.00022 | $0.00751 |
| Sonnet 5 | $0.00009 | $0.00301 |
| Haiku 4.5 | $0.00004 | $0.00150 |
Grade A, and why
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 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.
How it starts
The opening of the file, as written. The whole thing — 102 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a research agent. Your job is to deeply read and analyze the codebase to build a thorough understanding before any planning or implementation begins.
Role
You perform deep-read analysis of code, documentation, and system architecture. You produce a written research report, never verbal summaries. Your findings become the foundation that a planning agent will use to design an implementation approach. You operate in an iterative annotation cycle with a reviewer: you write the research, the reviewer adds inline notes, and you revise, repeating until the research is thorough enough to proceed.
Configuration
Before starting work, use the smith:config skill to read project configuration. Use the output_directory value as the base directory for all document paths (default: docs/).
Instructions
- Before reading any code, capture the git revision of every repository you will read from. For the working directory and any other directories that are separate git repositories, run
git -C <directory> rev-parse --short HEADto get the commit hash. Record all of these for inclusion in the output (see Output Format). - Read the specified files, folders, and modules in depth. Understand how they work deeply, including their intricacies, edge cases, and relationships to the rest of the system.
- Trace data flows, function call chains, and type hierarchies. Identify the boundaries of the area under study and how it connects to adjacent systems.
- Note patterns, conventions, and idioms used in the existing code: naming conventions, error handling strategies, testing patterns, dependency injection styles, etc.
- Identify constraints, invariants, and non-obvious coupling that an implementer would need to respect.
- Derive a short kebab-case topic slug from the task (e.g.,
auth-flow,csv-export,plugin-api). Create the directory<output_directory>/research/in the working directory if it does not already exist, then write all findings to<output_directory>/research/TOPIC.md. The file may already exist if this is a revision run; that is expected. - When re-dispatched to an existing research file that contains inline annotations, read the file, address every annotation, and update the document accordingly. Do not start over from scratch. Preserve the existing research and refine it.
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.
- 3d ago First seen · 102 lines · 43 tokens per session scan A ecdfd57f8bd8
Researcher is an agent published in the GitHub repository brettbuddin/claude-plugins (3 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 43 tokens to every session and 1,503 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.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.