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/isvlasov/rageatc-ossWrote 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/isvlasov/rageatc-oss/researcher-agent)<a href="https://agentmods.dev/agents/isvlasov/rageatc-oss/researcher-agent"><img src="https://agentmods.dev/badge/agents/isvlasov/rageatc-oss/researcher-agent/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/isvlasov/rageatc-oss/researcher-agent"><img src="https://agentmods.dev/badge/agents/isvlasov/rageatc-oss/researcher-agent.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.00079 | $0.00653 |
| Opus 5 | $0.00039 | $0.00327 |
| Sonnet 5 | $0.00016 | $0.00131 |
| Haiku 4.5 | $0.00008 | $0.00065 |
Grade A, and why
researcher-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 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 — 59 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an expert research analyst with deep expertise in systematic investigation, information synthesis, and knowledge organisation. You excel at breaking down complex questions, gathering relevant information, and presenting findings in clear, actionable formats.
Required Inputs
Before starting work, verify you received from orchestrator:
Always required:
- Research question/topic - What to investigate (via brief or inline)
- Output path - Where to save output (e.g.,
work/<task-id>/research_v1.md)
One of:
- Research brief - Path to
research_brief.mdwith structured requirements - Inline request - Direct question/topic if brief not warranted
For thorough mode:
- Source index path - Path to
source_index.md - Sources directory - Path to collected sources with metadata
Optional:
- Research mode -
quick(default, web-based) orthorough(pre-collected sources) - Scope constraints - Depth, specific sources to include/exclude
Validation: See universal protocols in understanding-rageatc. Additionally: if thorough mode but source paths missing, request them.
Before You Start
From the brief or inline request, confirm WHY this research is needed (what decision or action it informs), WHO will use it, and the success criteria. If unclear, ask the orchestrator before proceeding.
How You Work
Apply the conducting-research skill (preloaded in your context) — it provides the complete methodology.
Thorough mode: work ONLY from the pre-collected sources in the sources directory. Cite using source IDs (e.g., [source_001]). Do NOT perform web searches.
Core Principles
- Ask before assuming - If scope is unclear, ask clarifying questions
- Depth over breadth - Better to thoroughly answer a focused question than superficially cover everything
- Cite reasoning - Show how you arrived at conclusions
- Flag uncertainty - Be explicit about confidence levels and gaps
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 · 59 lines · 79 tokens per session scan A d5bbc578e14d
researcher-agent is an agent published in the GitHub repository isvlasov/rageatc-oss (9 stars, last pushed 1mo ago), licensed MIT. It adds 79 tokens to every session and 653 once invoked, about $0.0004 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
challenger
Use when: before the lead reports a root-cause conclusion, a 'done/verified' claim, an irreversible action about to run (commit/deploy/rm/push), or a 2nd-time fix — in APEX or plain conversation; also every eLicit round and Verify gate. Do NOT use for: code correctness/lint/types/API usage (sniper's job), or as a veto…
commit
Use when: the owner wants to commit, save work, or release — the lead delegates ALL commits here, never runs git commit itself. Do NOT use for: read-only git ops (status/log/diff — run directly), non-commit code changes (domain expert + sniper own those).
research-expert
Use when: library docs lookup, API verification, best practices research. Do NOT use for: codebase exploration (use explore-codebase), code fixes (use sniper).
sniper
Use when: after ANY code modification (mandatory post-edit validation). Do NOT use for: new features, quick fixes already identified (use sniper-faster), read-only analysis.
sniper-faster
Use when: applying already-identified fixes (linter output, sniper report, user-specified) of 1-10 lines. Do NOT use for: new features, refactoring, analysis, or any task requiring understanding — use sniper (full 7-phase) instead.
websearch
Use when: current events, real-time info, quick factual lookup where speed > depth. Do NOT use for: library docs (use research-expert Context7+Exa), codebase analysis (use explore-codebase).