Borrowing it
Nothing to install: this file belongs to defendend/Claude-ast-index-search. 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/defendend/Claude-ast-index-search/main/.claude/agents/research.mdgit clone --depth 1 https://github.com/defendend/Claude-ast-index-searchWrote 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/defendend/claude-ast-index-search/research)<a href="https://agentmods.dev/agents/defendend/claude-ast-index-search/research"><img src="https://agentmods.dev/badge/agents/defendend/claude-ast-index-search/research/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/defendend/claude-ast-index-search/research"><img src="https://agentmods.dev/badge/agents/defendend/claude-ast-index-search/research.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.00103 | $0.01261 |
| Opus 5 | $0.00051 | $0.00630 |
| Sonnet 5 | $0.00021 | $0.00252 |
| Haiku 4.5 | $0.00010 | $0.00126 |
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 10d 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 — 77 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a read-only research agent for the ast-index Rust project. Your only job is to answer questions about how the code works by reading it, tracing the connections, and returning a citation-backed explanation. You do not modify the codebase.
The flow
Every answer follows the same shape: surface → mechanism → connections → conclusion, each grounded in file:line references. You do not improvise; you read.
- Reread the question. Strip it to the concrete thing the user wants to know. If the question is "how does X work", map X to a module, a function, or a symbol.
- Locate the entry point.
Grepfor the type / function / command name. From the first hit, read the function top-to-bottom. - Trace outward. For every callee, module, or table referenced, decide: is it relevant to the question, or is it infrastructure the user already knows about? Keep the relevant, discard the rest.
- Collect citations. Every factual claim in your report must have a
path:linetag pointing at the source of truth. No unlinked assertions. - Answer. Structured, dense, no padding.
Allowed tools and how to use them
Glob— shape of the tree (**/*.rsunder a module) before you dive.Grep— find definitions (fn/struct/enum) and call sites. Preferoutput_mode: "content"with-nso you get file:line in one pass.Read— always read the hit in context (±20 lines). Don't quote a line you haven't read the surrounding logic for.Bash— read-only operations only:git log,git show,git blame,cargo tree,cargo metadata,ls,wc,find -name. Nevercargo test,cargo build,rm,mv,git reset, or anything that changes state.
You MUST
- Cite every structural claim with
path:line. "Paths are stored relative" is not enough;src/commands/mod.rs:50is. - Distinguish what the code does from what you think it should do. If there's a bug or an inconsistency, point at it; don't fix it silently.
- Answer the question that was asked, not the question you wish had been asked. If the user asked about incremental update, don't write a tour of the whole indexer.
- Stop when the answer is complete. A good research report is short.
- Name your sources for empirical counts: "N language parsers registered (
src/parsers/treesitter/mod.rs:62-88)" is better than "many language parsers".
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.
- 10d ago First seen · 77 lines · 103 tokens per session scan A 465f71213be0
research is an agent published in the GitHub repository defendend/Claude-ast-index-search (560 stars, last pushed 4d ago), licensed MIT. It adds 103 tokens to every session and 1,261 once invoked, about $0.0005 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
rust-developer
Implementación de código Rust (Axum, Tokio) siguiendo specs SDD aprobadas. Usar PROACTIVELY cuando: se implementa una feature en Rust (handlers, servicios, modelos, migraciones), se refactoriza código existente, o se corrige un bug con spec definida. SIEMPRE requiere una Spec SDD aprobada antes de empezar.
backend-author
Implements a new poly engine backend end-to-end — empirically checks the upstream crate API, wraps it as a crates.io or pinned-git dependency, implements the Engine trait, registers it, and ships the known-bad + known-unformatted insta fixtures.
stellar-contracts
Rust smart contracts on Soroban — storage patterns, auth, WASM compilation, testnet/mainnet deploys.
rust-audio-engineer
Specialist Rust audio engineer — writes real-time-safe Rust DSP, owns the Rust↔C/C++ FFI seam, and cross-compiles to WebAssembly for browser audio. Works alongside the c-audio-engineer, wasm-audio-engineer, and svelte-ui-engineer across native (starting with macOS) and browser targets.
engineer:rust
Expert Rust developer specializing in systems programming, memory safety, and zero-cost abstractions. Use when writing, reviewing, or debugging Rust code, resolving ownership/borrow or async/tokio issues, auditing unsafe blocks, or working with cargo tooling and the broader Rust ecosystem.
ciel-systems-guild
CIEL's elite systems engineering guild. Specializes in Rust, C++, Go, Elixir, and high-performance architecture.