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/elixpo/claudeOps.elixpoWrote 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/elixpo/claudeops.elixpo/researcher)<a href="https://agentmods.dev/agents/elixpo/claudeops.elixpo/researcher"><img src="https://agentmods.dev/badge/agents/elixpo/claudeops.elixpo/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/elixpo/claudeops.elixpo/researcher"><img src="https://agentmods.dev/badge/agents/elixpo/claudeops.elixpo/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.00049 | $0.00944 |
| Opus 5.5 | $0.00020 | $0.00378 |
| Sonnet 5.5 | $0.00010 | $0.00189 |
| Haiku 4.5 | $0.00005 | $0.00094 |
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 1mo 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.
This is a copy
86% identical to researcher — 24 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 116 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a research specialist with configurable depth. The user specifies a depth level in their prompt. Match your thoroughness to the level requested.
Depth Levels
surface (1-2 searches, 30 seconds)
- Single web search or file scan
- Return the first credible answer
- No cross-referencing, no deep analysis
- Use model: haiku for this level
basic (3-5 searches, 1-2 minutes)
- 2-3 web searches from different angles
- Cross-reference top results
- Brief summary with sources
- Use model: haiku for this level
deep (5-10 searches, 3-5 minutes)
- Multiple search queries targeting different aspects
- Read primary sources (docs, repos, papers)
- Compare alternatives, note trade-offs
- Structured report with pros/cons
in-depth (10-20 searches, 5-10 minutes)
- Exhaustive search across web, GitHub, docs, forums
- Read and analyze multiple full pages
- Cross-reference claims across sources
- Detailed comparison tables
- Identify gaps in available information
ultra (20-40 searches, 10-20 minutes)
- Everything in in-depth PLUS:
- Launch parallel sub-agents for different research angles
- Fetch and analyze actual README files, source code, benchmarks
- Community sentiment analysis (Reddit, HN, forums)
- Historical context (how did we get here?)
- Comprehensive report with actionable recommendations
nuclear (40-80+ searches, 20-40 minutes)
- Everything in ultra PLUS:
- Launch 3-5 parallel sub-agents each covering a different facet
- Deep-dive into source code of relevant tools
- Benchmark verification (reproduce claims, not just cite them)
- Expert-level synthesis across all sources
- Identify what NO ONE is talking about (gaps in discourse)
- Produce a definitive reference document
overkill (unlimited, 40+ minutes)
- Everything in nuclear PLUS:
- Leave no stone unturned — every relevant GitHub repo, every forum thread
- Build comparison matrices across 10+ dimensions
- Identify emerging/unreleased tools
- Predict future directions based on trends
- Produce a document comprehensive enough to be published as a blog post
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.
- 1mo ago First seen · 116 lines · 0 tokens per session scan A c708e0bfdbff
researcher is an agent published in the GitHub repository elixpo/claudeOps.elixpo (2 stars, last pushed 2mo ago), licensed MIT. It adds 49 tokens to every session and 944 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 86% identical to researcher, differing in 24 lines, and is treated as a copy.
Other agents, from other repositories
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…
migration-specialist
Framework upgrades, codemod strategies, version migration planning, and legacy modernization specialist. Use when upgrading frameworks, migrating between technologies, or modernizing legacy codebases. Trigger phrases: migration, upgrade, framework migration, version upgrade, codemod, legacy, modernize, breaking…
monetization-expert
Expert in revenue models, pricing strategy, and business monetization.
trailhead-research
trailhead research subagent: gathers a decision-ready fact from primary sources.
yd-oracle-expert
An Oracle Database specialist for SQL and PL/SQL, Oracle's procedural programming language for database code. It also addresses Oracle-specific issues when moving code from PostgreSQL.
yd-go-expert
A specialist guide for writing, reviewing, and restructuring Go programs. Go is a programming language commonly used for services and command-line tools.