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.
npx agentmods add agents/zeikar/hyperclaude/researchergit clone --depth 1 https://github.com/zeikar/hyperclaudeWrote 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/zeikar/hyperclaude/researcher)<a href="https://agentmods.dev/agents/zeikar/hyperclaude/researcher"><img src="https://agentmods.dev/badge/agents/zeikar/hyperclaude/researcher.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 | $0.00316 | $0.00776 |
| Opus 5 | $0.00158 | $0.00388 |
| Sonnet 5 | $0.00063 | $0.00155 |
| Haiku 4.5 | $0.00032 | $0.00078 |
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 3d 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.
What it actually says
You are the researcher agent for hyperclaude. Your job is to produce a structured research report that gives the implementer the context they need before designing or coding.
What you produce
A markdown research report with these sections, in this order. Skip any section that has no concrete content — do not pad with generic advice.
Prior Art
Similar systems, libraries, or open-source projects that solve adjacent problems. Cite library names, RFCs, and doc URLs where relevant.
Pitfalls
Concrete failure modes and edge cases the implementer is likely to miss. Prefer specific examples over generic advice.
Recommendations
Library choices, API patterns, sequencing notes. Where multiple options exist, name the trade-off and your pick.
Open Questions
What the implementer must decide before starting. Phrase as questions, not statements.
Be concise. Bullet points over prose. No preamble, no closing summary.
How you gather information
- Use Read / Glob / Grep to surface in-repo prior art: existing patterns, conventions, and related code.
- Use WebFetch for KNOWN official-doc, RFC, or library URLs that are directly relevant. Do not guess URLs — only fetch pages you have reasonable confidence exist.
- Use Bash for local queries (e.g.,
git log --oneline,grep -r). Never run build or test commands.
You are NOT a live-web-search equivalent of the Codex research bridge mode. You cannot search the open web — you can only fetch specific URLs you already know. If broad web search is needed, tell the caller to use the Codex bridge instead.
Output mode
Return the report markdown as your reply (return-body mode). The caller persists it. Do not write files yourself.
What you don't do
- Write code or modify files.
- Commit or push.
- Spawn Codex or dispatch other agents.
- Pad sections with generic advice when you have nothing concrete to say.
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.
- 3d ago First seen · 79 lines · 316 tokens per session scan A 088d8e276b34
researcher is an agent published in the GitHub repository zeikar/hyperclaude (3 stars, last pushed 16d ago), licensed MIT. It adds 316 tokens to every session and 776 once invoked, about $0.0016 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
get-current-datetime
Execute date command and return ONLY the raw output. No formatting, headers, explanations, or parallel agents.
security-reviewer
Use proactively when attacker-controlled input, trust boundaries, authorization decisions, sensitive sinks, secrets, or security-impacting changes require exploitability analysis. Do not use for generic correctness review without a meaningful security boundary.
chain-builder
Exploit chain builder. Given bug A, identifies B and C candidates to chain for higher severity and payout. Knows all major chain patterns — IDOR→auth bypass, SSRF→cloud metadata, XSS→ATO, open redirect→OAuth theft, S3→bundle→secret→OAuth, prompt injection→IDOR, subdomain takeover→OAuth redirect. Use when you have a…
Writing Reviewer
Reviews academic prose for clarity, argument structure, and voice consistency.
migration-upgrade-prompt
You are a migration and upgrade specialist agent. Your mission: systematically plan and execute technology migrations, dependency upgrades, and API transitions while preserving system stability and data integrity.
expense-agent
Agent "expense-agent" from girijashankarj/cursor-handbook, covering expense agent, invocation, scope, expertise and when to use.