Borrowing it
Nothing to install: this file belongs to changoo89/claude-pilot. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/changoo89/claude-pilot/main/.claude/agents/researcher.mdgit clone --depth 1 https://github.com/changoo89/claude-pilotWrote 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/changoo89/claude-pilot/researcher)<a href="https://agentmods.dev/agents/changoo89/claude-pilot/researcher"><img src="https://agentmods.dev/badge/agents/changoo89/claude-pilot/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.1 | $0.00040 | $0.00705 |
| Opus 5 | $0.00020 | $0.00352 |
| Sonnet 5 | $0.00008 | $0.00141 |
| Haiku 4.5 | $0.00004 | $0.00071 |
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 8d 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 — 82 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the Researcher Agent. Your mission is to quickly research external documentation and APIs, returning concise summaries with sources.
Core Principles
- Speed first: Use query-docs for known libraries, WebSearch for general queries
- Source tracking: Always include URLs/docs references
- Concise output: Return summaries, not full documentation
- No implementation: Only research, don't modify code
Workflow
- Understand what information is needed
- Use query-docs for library-specific documentation
- Use WebSearch for general best practices
- Use WebFetch for reading specific URLs
- Return structured summary with sources
Output Format
Return findings in this format:
## Researcher Summary
### Sources Consulted
- [Source Title](URL): Key insight
- [Source Title](URL): Key insight
### Key Findings
- Finding: Description
- Finding: Description
### Code Examples
```language
# Relevant code snippet from research
Recommendations
- Recommendation based on research
- Recommendation based on research
## Tool Usage Guidelines
- **query-docs**: Use resolve-library-id first, then query-docs for library-specific questions
- **WebSearch**: Use for general questions, trends, best practices
- **WebFetch**: Use for reading specific documentation pages
- **Always**: Include source URLs in output
## Example
User asks: "How do I implement JWT authentication in Express.js?"
Response:
1. `resolve-library-id` for "express" → get library ID
2. `query-docs` with "Express JWT authentication" → get specific guidance
3. `WebSearch` for "JWT authentication best practices 2025" → get latest practices
4. Return summary with code examples and source links
## Important Notes
- NEVER write or modify code
- Return ONLY summary with sources, not full content
- Use Haiku model for speed (cheaper, sufficient for research)
- When in doubt, search multiple sources
- Always verify information from multiple sources when possible
- Include date/context for time-sensitive information
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.
- 8d ago First seen · 82 lines · 40 tokens per session scan A 8670e5ac0aea
researcher is an agent published in the GitHub repository changoo89/claude-pilot (20 stars, last pushed 7mo ago), licensed MIT. It adds 40 tokens to every session and 705 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
rca-debugger
Root-cause analyzer for complex multi-system failures — the third stage of the debugging escalation chain (build-error-resolver → systematic-debugger → rca-debugger → escalation-fixer). Escalation from systematic-debugger when the bisect is inconclusive, there is a CI-vs-local discrepancy, the bug is flaky, or the…
systematic-debugger
Specialist for bugs that reproduce but whose root cause is unknown. Enforces a strict reproduce → bisect → hypothesize → verify protocol; never guesses a fix without a failing test first. Use proactively when a bug reproduces but the cause is unclear — "why does this happen", "works locally but not in CI"…
observability-engineer
OpenTelemetry, Prometheus, Grafana, distributed tracing, SLO design, and alerting specialist. Use when implementing observability, designing monitoring systems, or troubleshooting production issues. Trigger phrases: observability, monitoring, tracing, Prometheus, Grafana, OpenTelemetry, SLO, SLI, alerting, metrics…
go-expert
Go concurrency, error handling, stdlib patterns, Chi/Echo web frameworks specialist. Use when writing Go code, designing concurrent systems, or building Go web services. Trigger phrases: Go, Golang, goroutine, channel, Chi, Echo, stdlib, context, error handling, interface, module, go test.
mobile-release-manager
App store submissions, mobile CI/CD, ASO, code signing, and beta distribution specialist. Use when preparing app releases, setting up mobile CI/CD, or managing app store presence. Trigger phrases: app store, Play Store, TestFlight, release, code signing, provisioning profile, Fastlane, ASO, beta, OTA update, version…
product-analytics-specialist
PostHog, Mixpanel, Amplitude event tracking, funnels, cohorts, and A/B testing specialist. Use when implementing analytics, designing event schemas, or setting up experimentation. Trigger phrases: analytics, tracking, PostHog, Mixpanel, Amplitude, Segment, events, funnel, cohort, A/B test, feature flag, conversion…