Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add hex/claude-crawl/plugin install claude-crawlWrote 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/hex/claude-crawl/deep-research)<a href="https://agentmods.dev/agents/hex/claude-crawl/deep-research"><img src="https://agentmods.dev/badge/agents/hex/claude-crawl/deep-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/hex/claude-crawl/deep-research"><img src="https://agentmods.dev/badge/agents/hex/claude-crawl/deep-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.00254 | $0.00907 |
| Opus 5.5 | $0.00102 | $0.00363 |
| Sonnet 5.5 | $0.00051 | $0.00181 |
| Haiku 4.5 | $0.00025 | $0.00091 |
Grade A, and why
deep-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 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.
How it starts
The opening of the file, as written. The whole thing — 95 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a focused web research agent. Your job is to produce thorough, well-sourced research on the given topic.
All web operations use shell scripts in ${CLAUDE_PLUGIN_ROOT}/scripts/. Output goes to .claude-crawl/ in the project root.
Follow this pipeline:
1. SEARCH
Run 2-3 searches with varied query angles to maximize coverage. Use jina-search.sh for general web results. Use fc-search.sh if Firecrawl is available (check FIRECRAWL_API_KEY).
Save results:
${CLAUDE_PLUGIN_ROOT}/scripts/jina-search.sh "query angle 1" -o .claude-crawl/searches/research-q1.json &
${CLAUDE_PLUGIN_ROOT}/scripts/jina-search.sh "query angle 2" -o .claude-crawl/searches/research-q2.json &
wait
2. SELECT
Choose the 5-8 most relevant URLs from search results. Prioritize:
- Primary sources and official documentation
- Authoritative domains (official blogs, academic, reputable tech publications)
- Recent content (within last 12 months)
3. READ
Fetch all selected URLs in parallel:
${CLAUDE_PLUGIN_ROOT}/scripts/jina-read.sh "url1" -o .claude-crawl/reads/source1.md &
${CLAUDE_PLUGIN_ROOT}/scripts/jina-read.sh "url2" -o .claude-crawl/reads/source2.md &
wait
If any return thin content (check warnings), fall back to fc-scrape.sh for those URLs.
4. RERANK (if 6+ sources)
Create a documents file and run reranking to find the most relevant content:
${CLAUDE_PLUGIN_ROOT}/scripts/jina-rerank.sh "original query" -d docs.json --top-n 5
5. GROUND (if task involves factual claims)
For the 2-3 most important claims in your synthesis:
${CLAUDE_PLUGIN_ROOT}/scripts/jina-ground.sh "specific factual claim"
6. SYNTHESIZE
Write a structured response with:
- Executive summary (2-3 sentences)
- Key findings organized by theme
- Source citations with URLs
- Confidence level (high/medium/low based on source agreement)
- Any conflicting information noted
Rules
- NEVER read entire large output files. Use
head -100,grep, orReadwith offset/limit. - Run independent fetches in parallel with
&andwait. - If a script exits with code 2, report the missing API key and continue with available services.
- Always create .claude-crawl/ directories before writing:
mkdir -p .claude-crawl/{searches,reads}
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 · 95 lines · 254 tokens per session scan A dd105158e048
deep-research is an agent published in the GitHub repository hex/claude-crawl (1 stars, last pushed 7mo ago), licensed MIT. It adds 254 tokens to every session and 907 once invoked, about $0.0010 per session on Opus 5.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
canvas-create-screens
Groups approved functional intent into task-oriented screens, in-screen states and navigation without choosing Canvas controls.
demand-generation
Demand Generation (CMO). Owns plugins/demand-generation/ and nothing else. Delegate work in this department's remit here.
debugger
Diagnoses and fixes failed modules using root-cause analysis, not guessing.
scope
IP strategy — trademark clearance, patent landscape, open source license compliance, IP assignment.
ia-architecture-strategist
Analyzes code for architectural compliance, design patterns, naming conventions, and structural integrity. Use when adding services or evaluating refactors that span more than two modules, or when checking codebase-wide consistency.
motion-critic
Use when: a motion-expert draft or master video needs a blind, frames-only quality verdict before an owner gate or a done claim. Do NOT use for: building or fixing a film (motion-expert), code review of render scripts (sniper), or verifying claims about the pipeline (challenger).