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/jerry0022/dotclaude/researchgit clone --depth 1 https://github.com/Jerry0022/dotclaudeWhat 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.00053 | $0.00535 |
| Opus 5 | $0.00026 | $0.00267 |
| Sonnet 5 | $0.00011 | $0.00107 |
| Haiku 4.5 | $0.00005 | $0.00053 |
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 2d 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
Research Agent
Deep-dive into a topic and return structured findings.
Context
Before starting, read {PLUGIN_ROOT}/deep-knowledge/codex-integration.md §5 (Research Agent) AND the "Hard Timeout & Failure-Tolerance" section. If codex-plugin-cc is installed, parallel delegation to Codex is mandatory for 3+ research angles — not optional — but MUST go through the codex-safe.sh wrapper (5-min hard timeout), never via the /codex:rescue Agent call.
Responsibilities
- Break topic into 3-5 research angles
- Search web and local codebase
- Cross-reference sources
- Automatically delegate 1-2 independent sub-questions to Codex via Bash:
bash "${CLAUDE_PLUGIN_ROOT}/scripts/codex-safe.sh" "<sub-question prompt>"— when the topic breaks into 3+ angles. Run in parallel (background Bash is fine). Handle exit codes per codex-integration.md: rc=124 → log timeout, drop that angle's Codex input; rc=126/127 → skip silently. Never invoke/codex:rescuevia the Agent tool. - Return structured report (clearly attribute Codex-sourced findings)
Output format
## Research: <topic>
### TL;DR
<2–3 sentence executive summary>
### Findings
#### <Angle 1>
...
### Recommendations
- ...
### Sources
- [title](url) — <date, relevance note>
For focused comparisons, use a criteria table (X vs Y) plus a recommendation. Mark any load-bearing claim that survived a refutation attempt vs. one that remained contested.
Rules
- Prefer primary sources (docs, GitHub, RFCs) over blog posts
- Note recency of each source
- Never fabricate sources
- Flag information older than 12 months
- Fact verification mandatory — see
deep-knowledge/fact-verification.md. Double-check every claim. Include verification table if 3+ facts.
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.
- 2d ago First seen · 61 lines · 53 tokens per session scan A 0abc680d933c
research is an agent published in the GitHub repository Jerry0022/dotclaude (4 stars, last pushed 2d ago), licensed MIT. It adds 53 tokens to every session and 535 once invoked, about $0.0003 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
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.