Borrowing it
Nothing to install: this file belongs to grandinh/claude-chaos-express. 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/grandinh/claude-chaos-express/main/.claude/agents/research-expert.mdgit clone --depth 1 https://github.com/grandinh/claude-chaos-expressWrote 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/grandinh/claude-chaos-express/research-expert)<a href="https://agentmods.dev/agents/grandinh/claude-chaos-express/research-expert"><img src="https://agentmods.dev/badge/agents/grandinh/claude-chaos-express/research-expert/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/grandinh/claude-chaos-express/research-expert"><img src="https://agentmods.dev/badge/agents/grandinh/claude-chaos-express/research-expert.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.00026 | $0.01686 |
| Opus 5 | $0.00013 | $0.00843 |
| Sonnet 5 | $0.00005 | $0.00337 |
| Haiku 4.5 | $0.00003 | $0.00169 |
Grade A, and why
research-expert 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 11d 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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.
- 11d ago First seen · 231 lines · 26 tokens per session scan A 1158f50702ec
research-expert is an agent published in the GitHub repository grandinh/claude-chaos-express (2 stars, last pushed 9mo ago), with no licence file. It adds 26 tokens to every session and 1,686 once invoked, about $0.0001 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
your-agent-name
Brief description of what this agent does (1-2 sentences).
research-expert
Specialized research expert for parallel information gathering. Use for focused research tasks with clear objectives and structured output requirements.
astro-file-editor
Expert in creating and editing .astro files for landing pages with Astro framework, Tailwind CSS v4, and shadcn/ui components. Use PROACTIVELY for creating pages, components, layouts, or converting React/JSX to .astro format.
code-review-expert
Deep code review specialist using a 9-layer methodology — root cause analysis, cross-file intelligence, and impact-based prioritization. Use PROACTIVELY after significant code changes, refactors, or before merging PRs.
git-expert
Git workflow, merge conflict, and repository recovery expert. Use PROACTIVELY for merge conflicts, rebase failures, history rewriting, detached HEAD, lost commits, branching strategy decisions, or any git error message you cannot resolve.
refactoring-expert
PROACTIVELY invoke when encountering duplicated code, long methods, complex conditionals, deep nesting, primitive obsession, or any structural code quality issue. Detects code smells and applies proven refactoring techniques without changing external behavior.