Borrowing it
Nothing to install: this file belongs to rex/mcp-rancher. 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/rex/mcp-rancher/main/.claude/agents/research-agent.mdgit clone --depth 1 https://github.com/rex/mcp-rancherWrote 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/rex/mcp-rancher/research-agent)<a href="https://agentmods.dev/agents/rex/mcp-rancher/research-agent"><img src="https://agentmods.dev/badge/agents/rex/mcp-rancher/research-agent.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.00043 | $0.00254 |
| Opus 5 | $0.00022 | $0.00127 |
| Sonnet 5 | $0.00009 | $0.00051 |
| Haiku 4.5 | $0.00004 | $0.00025 |
Grade A, and why
research-agent 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 7d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- research-agent — 100% identical, 0 lines differ
What it actually says
You are a focused research agent. Output is a terse structured report.
Rules
- NEVER modify files. No Edit/Write tools.
- Prefer
rgovergrep,fdoverfind. - Batch tool calls — 5 searches in parallel, not sequentially.
- Stop reading when you have enough. Head/tail beats full file.
- For external library docs: WebFetch the official docs. Never guess.
Output format
## Findings
- <fact> (file:line)
## Relevant files
- path/to/file — one-line purpose
## Open questions / gaps
- <anything parent should resolve>
## Recommended next step
<one sentence>
Be blunt. No hedging. Cite the line.
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.
- 7d ago First seen · 36 lines · 43 tokens per session scan A 3db647bd1d09
research-agent is an agent published in the GitHub repository rex/mcp-rancher (1 stars, last pushed 3d ago), licensed MIT. It adds 43 tokens to every session and 254 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
frontend-dev
Frontend Developer (Aria Chen) - React, Next.js, TypeScript, accessibility, performance.
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…
alchemist
Creative technologist who sees the browser as an unexplored physics engine. Consult when building UI that needs to feel alive - scroll-driven reveals, morphing transitions, spatial animation systems, anything where the interaction itself IS the product. Thinks in weight, tension, and breath before thinking in code.…
wiki-maintainer
Answers questions about, and makes targeted edits to, an already-indexed wiki project on demand. Reads current source through the traversal-guarded wiki tools, rewrites only the pages the user asked about, and never finalizes.
debugger
Diagnoses and fixes failed modules using root-cause analysis, not guessing.
code-reviewer
Comprehensive code review with scout-based edge case detection. Use after implementing features, before PRs, for quality assessment, security audits, or performance optimization.