setup

A setup command for a web-crawling project that checks available service credentials and creates its working folders.

In plain words
What is it for?
Use it when initializing the project before searching, reading, crawling, extracting, reranking, taking screenshots, or creating PDFs.
Why use it?
It shows which web services are ready and records crawl-related output in a dedicated directory that can be excluded from version control.

Command

Install

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.

agentmods
npx agentmods add commands/hex/claude-crawl/setup
Clone the repo
git clone --depth 1 https://github.com/hex/claude-crawl
Per session 18 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 237 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00018 $0.00237
Opus 5 $0.00009 $0.00118
Sonnet 5 $0.00004 $0.00047
Haiku 4.5 $0.00002 $0.00024

Measured yesterday against content hash 5b458a8d2818, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

setup 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 yesterday.

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.

commands/setup.md · 18 lines

What it actually says

Run setup for claude-crawl:

  1. Run bash ${CLAUDE_PLUGIN_ROOT}/scripts/check-auth.sh --verbose and show the output.
  2. Create the output directory structure:
    mkdir -p .claude-crawl/{reads,searches,crawls,extractions,reranks,ground,screenshots,pdfs}
    
  3. Add .claude-crawl/ to .gitignore if it exists and the entry is not already there.
  4. Report which services are available based on check-auth output, and how to set any missing keys:
    • export JINA_AI_API_KEY=... — for Jina Reader, Search, Reranker, Grounding
    • export FIRECRAWL_API_KEY=... — for Firecrawl scrape, crawl, map, search
    • export CLOUDFLARE_API_TOKEN=... and export CLOUDFLARE_ACCOUNT_ID=... — for Cloudflare Browser Rendering
Changes

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.

  1. yesterday First seen · 18 lines · 18 tokens per session scan A 5b458a8d2818

Subscribe to this mod's changes

setup is a command published in the GitHub repository hex/claude-crawl (1 stars, last pushed 5mo ago), licensed MIT. It adds 18 tokens to every session and 237 once invoked, about $0.0001 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.