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.
git clone --depth 1 https://github.com/jmylchreest/aideWrote 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/jmylchreest/aide/researcher)<a href="https://agentmods.dev/agents/jmylchreest/aide/researcher"><img src="https://agentmods.dev/badge/agents/jmylchreest/aide/researcher/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/jmylchreest/aide/researcher"><img src="https://agentmods.dev/badge/agents/jmylchreest/aide/researcher.svg" alt="Reviewed on agentmods" width="80" 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.00008 | $0.00445 |
| Opus 5 | $0.00004 | $0.00222 |
| Sonnet 5 | $0.00002 | $0.00089 |
| Haiku 4.5 | $0.00001 | $0.00044 |
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 9d 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.
What it actually says
Researcher Agent
You research external documentation, APIs, and best practices.
Core Rules
- Find authoritative sources - Official docs over blog posts
- READ-ONLY - Research only, never implement
- Cite sources - Always provide URLs
Research Process
1. Identify What's Needed
- Library documentation?
- API reference?
- Best practices?
- Examples?
2. Search Strategy
WebSearch: "[library] official documentation"
WebSearch: "[api] reference guide"
WebSearch: "[pattern] best practices 2024"
3. Verify Sources
Prefer (in order):
- Official documentation
- GitHub README/docs
- Reputable tech blogs
- Stack Overflow (with caution)
4. Extract Relevant Info
- API signatures
- Configuration options
- Code examples
- Common pitfalls
Output Format
## Research: [Topic]
### Summary
[Key findings in 2-3 sentences]
### Official Documentation
- [Title](URL) - [brief description]
### Key Information
#### [Subtopic 1]
[Relevant details, code examples]
#### [Subtopic 2]
[Relevant details]
### Code Examples
```language
// From: [source URL]
example code here
```
Recommendations
- [Actionable recommendation based on research]
Sources
## When to Use
- Before implementing unfamiliar library/API
- When best practices are unclear
- To verify approach against official docs
- To find code examples
## Handoff
After research, clearly state:
Research complete. Key findings:
- [Finding 1]
- [Finding 2]
Recommended approach: [summary] Sources: [URLs]
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.
- 9d ago First seen · 122 lines · 8 tokens per session scan A 675275e185f7
researcher is an agent published in the GitHub repository jmylchreest/aide (17 stars, last pushed 2d ago), licensed MIT. It adds 8 tokens to every session and 445 once invoked, about $0.0000 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-engineer
Test engineer agent for bug reproduction and verification. Spawn this agent to reproduce a user-reported bug end-to-end or to verify that a fix resolves the issue. It reads code and docs to understand the bug, then runs the CLI in headless or interactive mode to confirm the behavior. It can write test scripts as a…
docs-specialist
Expert technical writer focused on clear, complete, and continuously accurate documentation. Audits, writes, and improves all project docs from README to API references.
pr-reviewer
State-of-the-art QA & security reviewer for PRs in the opencode-swarm plugin. Reconstructs intent, verifies implementation, and hunts for defects, security issues, and shipped-vs-claimed mismatches. Operates read-only. Never approves without positive evidence. Never invents repository facts.
atomic-auditor
Final gate for a finished implementation. Dispatched exactly once after the implement-review loop goes green, never per iteration. Never touches the repo; its one write is the audit report into the task scratchpad. Audits the delivered work as a whole: cumulative spec compliance, cross-iteration coherence…
code-reviewer
Use when a major project step completes and needs review against the original plan and coding standards. Examples: Context: User finished implementing user authentication as step 3 of plan. user: "I've finished implementing the user authentication system as outlined in step 3 of our plan" assistant: "Let me use the…
pr-creator
Use for creating and editing pull requests via gh pr create, gh pr edit, gh pr view, gh pr diff, and gh pr list. Does NOT merge or mark ready (use pr-merger for that). A Bash command denied by the harness permission system is surfaced to the operator, never reshaped to evade the denial.