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 skills add RudraDudhat2509/claude-skills --skill firecrawl-crawlgit clone --depth 1 https://github.com/RudraDudhat2509/claude-skillsWrote 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/skills/rudradudhat2509/claude-skills/firecrawl-crawl)<a href="https://agentmods.dev/skills/rudradudhat2509/claude-skills/firecrawl-crawl"><img src="https://agentmods.dev/badge/skills/rudradudhat2509/claude-skills/firecrawl-crawl/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/skills/rudradudhat2509/claude-skills/firecrawl-crawl"><img src="https://agentmods.dev/badge/skills/rudradudhat2509/claude-skills/firecrawl-crawl.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.00089 | $0.00613 |
| Opus 5 | $0.00044 | $0.00307 |
| Sonnet 5 | $0.00018 | $0.00123 |
| Haiku 4.5 | $0.00009 | $0.00061 |
Grade A, and why
firecrawl-crawl 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 12d 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 — 59 lines — stays where its author put it; the contents beside it link to each section on GitHub.
firecrawl crawl
Bulk extract content from a website. Crawls pages following links up to a depth/limit.
When to use
- You need content from many pages on a site (e.g., all
/docs/) - You want to extract an entire site section
- Step 4 in the workflow escalation pattern: search → scrape → map → crawl → interact
Quick start
# Crawl a docs section
firecrawl crawl "<url>" --include-paths /docs --limit 50 --wait -o .firecrawl/crawl.json
# Full crawl with depth limit
firecrawl crawl "<url>" --max-depth 3 --wait --progress -o .firecrawl/crawl.json
# Check status of a running crawl
firecrawl crawl <job-id>
Options
| Option | Description |
|---|---|
--wait |
Wait for crawl to complete before returning |
--progress |
Show progress while waiting |
--limit <n> |
Max pages to crawl |
--max-depth <n> |
Max link depth to follow |
--include-paths <paths> |
Only crawl URLs matching these paths |
--exclude-paths <paths> |
Skip URLs matching these paths |
--delay <ms> |
Delay between requests |
--max-concurrency <n> |
Max parallel crawl workers |
--pretty |
Pretty print JSON output |
-o, --output <path> |
Output file path |
Tips
- Always use
--waitwhen you need the results immediately. Without it, crawl returns a job ID for async polling. - Use
--include-pathsto scope the crawl — don't crawl an entire site when you only need one section. - Crawl consumes credits per page. Check
firecrawl credit-usagebefore large crawls.
See also
- firecrawl-scrape — scrape individual pages
- firecrawl-map — discover URLs before deciding to crawl
- firecrawl-download — download site to local files (uses map + scrape)
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.
- 12d ago First seen · 59 lines · 89 tokens per session scan A a5ddaae261c6
firecrawl-crawl is a skill published in the GitHub repository RudraDudhat2509/claude-skills (2 stars, last pushed 19d ago), licensed MIT. It adds 89 tokens to every session and 613 once invoked, about $0.0004 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 skills, from other repositories
agentcookie-install
Install agentcookie on a Mac source and a Linux or Mac sink so Chrome cookies sync continuously over Tailscale. Use when the user says "install agentcookie", "set up cookie sync", "share my Chrome sessions with my agent box", or "make my agent log in as me".
tauri-mcp-cli
Use the Tauri MCP CLI to start and recover driver sessions, automate Tauri webviews, capture UI state, debug IPC, and work with mobile or remote devices. Use whenever an agent needs to operate a Tauri v2 app from terminal commands.
browser-automation
A browser-automation workflow that detects the terminal environment and chooses a browser control tool. It supports opening pages, taking snapshots, clicking, filling fields, and other checks.
playwright-cli
Skill "playwright-cli" from Insajin/autopus-adk, covering browser automation with playwright-cli, quick start, commands, core and navigation.
goofish-overview
An overview and entry point for goofish-cli, a tool package for helping an AI agent operate Xianyu, a Chinese second-hand marketplace. It covers account checks, listing items, buyer messages, risk checks, and shop diagnosis, and directs specific jobs to dedicated workflows.
scout-web-access
Strato web-access cross-provider per gli Scout (F-2). 5 componenti coordinati — anti-bot robust scrape, LinkedIn session + search, email IMAP poll, multi-Scout workspace claim, freshness focus. Usato come stack base per ogni sweep: lo Scout sceglie il livello di accesso più leggero che funziona, e sale solo quando…