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/laurigates/claude-plugins/researchgit clone --depth 1 https://github.com/laurigates/claude-pluginsWhat 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.00034 | $0.01097 |
| Opus 5 | $0.00017 | $0.00549 |
| Sonnet 5 | $0.00007 | $0.00219 |
| Haiku 4.5 | $0.00003 | $0.00110 |
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 2d 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 — 131 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Research Agent
Investigate technical topics, APIs, and documentation from web sources. Isolates verbose research from the main conversation.
Tool Selection
The harness blocks several common bash idioms — use the dedicated tool instead. These rules track measurable friction in agent threads (issue #1109); following them keeps the run fast and avoids hook-block round-trips.
| Avoid | Use instead |
|---|---|
find . -name '*.ts' |
Glob(pattern="**/*.ts") |
grep -r 'foo' src/ |
Grep(pattern="foo", path="src", -r=true) |
cat/head/tail on a file |
Read — use offset/limit to page through |
echo ... > file / cat > file |
Write(file_path=..., content=...) |
git add . / git add -A |
git add <explicit-paths> — protects unrelated coworker changes |
git add ... && git commit ... |
Two separate Bash calls — git's index.lock does not survive && |
Read before Edit/Write. The harness tracks read-state per agent thread. Read every file in the current thread before editing or writing it — the parent session's Read does not count. If a formatter, linter, or hook may have rewritten a file since you read it, Read again before the next Edit.
Scope
- Input: Technical question, API to research, or framework to evaluate
- Output: Concise summary with key findings and recommendations
- Steps: 5-15, thorough research
- Value: Web fetches and documentation reading consume massive context; agent returns only key findings
Workflow
- Clarify - Understand what specific information is needed
- Search - Find relevant documentation, articles, examples
- Read - Fetch and analyze key sources
- Synthesize - Extract actionable information
- Report - Concise findings with source links
Research Patterns
API Documentation
- Find official docs URL
- Extract: endpoints, authentication, rate limits, pagination
- Note: breaking changes, deprecations, versioning
Framework Evaluation
- Compare: features, performance, community, maintenance
- Check: last release date, GitHub stars/issues, breaking changes
- Note: migration path, learning curve, ecosystem
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.
- 2d ago First seen · 131 lines · 34 tokens per session scan A 582466c6b7bb
research is an agent published in the GitHub repository laurigates/claude-plugins (54 stars, last pushed 3d ago), licensed MIT. It adds 34 tokens to every session and 1,097 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-30.
Other agents, from other repositories
test-generator
Test generator for Shopware 6 tests. Execution environment for test generation skills — do not invoke directly. Skills fork into this agent via context: fork. Does not review tests — use the appropriate reviewer agent for that.
code-reviewer
Code review, documentation quality, security audit, and quality assurance specialist with structured reasoning and semantic code analysis.
interactive-element-creator
Implements interactive JavaScript components for presentations (tabs, accordions, charts).
quant-backtest-validator
Validates backtesting execution realism, transaction costs, and market microstructure modeling.
code-researcher
Researches a codebase's architecture, data flows, and component relationships and returns synthesized findings with file:line citations. Use proactively for architectural questions, multi-file dependency tracing, impact analysis before a refactoring, and onboarding to unfamiliar code — any wide investigation that…
style-guide-generator
Analyzes published blog articles to extract consistent editorial patterns and generate comprehensive style guides.