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.
git clone --depth 1 https://github.com/firecrawl/firecrawl-claude-pluginWrote 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/commands/firecrawl/firecrawl-claude-plugin/setup)<a href="https://agentmods.dev/commands/firecrawl/firecrawl-claude-plugin/setup"><img src="https://agentmods.dev/badge/commands/firecrawl/firecrawl-claude-plugin/setup/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/commands/firecrawl/firecrawl-claude-plugin/setup"><img src="https://agentmods.dev/badge/commands/firecrawl/firecrawl-claude-plugin/setup.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.00013 | $0.00232 |
| Opus 5.5 | $0.00005 | $0.00093 |
| Sonnet 5.5 | $0.00003 | $0.00046 |
| Haiku 4.5 | $0.00001 | $0.00023 |
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.
What it actually says
Firecrawl setup
This plugin connects to Firecrawl's hosted MCP server. It needs no API key in the conversation and no CLI install.
- Check whether the Firecrawl tools are available in this session. If they are,
make one free call,
firecrawl_find_toolswith a short query, to confirm the account connection works. - If the tools are missing or the call reports a connection or authentication
error, tell the user to run
/mcp, select firecrawl, and complete the sign-in in the browser, then run/firecrawl:setupagain. - Never ask the user to paste an API key into the conversation.
When the check passes, say which commands are available: /firecrawl:search,
/firecrawl:scrape, /firecrawl:map, /firecrawl:crawl and
/firecrawl:agent. Plain requests work too; the firecrawl skill picks the
right tool.
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.
- yesterday First seen · 23 lines · 13 tokens per session scan A f7d54c44bdec
setup is a command published in the GitHub repository firecrawl/firecrawl-claude-plugin (248 stars, last pushed 2d ago), licensed MIT. It adds 13 tokens to every session and 232 once invoked, about $0.0001 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-10-26.
Other commands, from other repositories
psql-query
Run ad-hoc PostgreSQL analytics queries against dev/test database.
build
Mini spec-first development workflow for well-scoped implementation tasks with human in the loop.
esp-teach
One-time project setup -- discover hardware, find datasheets, persist context to CLAUDE.md.
swift-critique
Critique SwiftUI code for patterns, design, clean code, accessibility, and performance.
customer-persona-builder
Jobs-to-be-Done (JTBD) customer persona development with priority matrix, buying journey mapping, and decision criteria analysis. Creates actionable buyer personas for product and marketing decisions.
fundraising-strategy-planner
Create comprehensive fundraising playbook covering timeline, investor targeting, outreach cadence, meeting progression, due diligence preparation, term sheet negotiation, and closing process. Run disciplined fundraising that maximizes leverage and closes on favorable terms.