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 commands/maccman/growth-agents/setup-firecrawlgit clone --depth 1 https://github.com/maccman/growth-agentsWrote 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/maccman/growth-agents/setup-firecrawl)<a href="https://agentmods.dev/commands/maccman/growth-agents/setup-firecrawl"><img src="https://agentmods.dev/badge/commands/maccman/growth-agents/setup-firecrawl.svg" alt="Measured on agentmods" 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 | $0.00000 | $0.01466 |
| Opus 5 | $0.00000 | $0.00733 |
| Sonnet 5 | $0.00000 | $0.00293 |
| Haiku 4.5 | $0.00000 | $0.00147 |
Grade A, and why
setup-firecrawl 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 4d 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 — 167 lines — stays where its author put it; the contents beside it link to each section on GitHub.
When the user triggers this action, walk them through setting up Firecrawl for this project. Run each step automatically. Speak in plain, friendly language.
What is Firecrawl?
Firecrawl is a web data API that turns any website into clean, LLM-ready markdown or structured data. It handles proxies, rate limits, JavaScript-rendered pages, and anti-bot mechanisms so you don't have to. Key capabilities:
- Scrape — extract content from a single URL as markdown, HTML, JSON, screenshots, or links
- Crawl — scrape all pages of a website automatically
- Search — search the web and get full page content from results
- Map — discover all URLs on a site instantly
- Extract — get structured data from pages using AI prompts and schemas
- Agent — gather data from the web using natural language prompts
- Browser — launch cloud browser sessions for interactive scraping
When to use the CLI vs the SDK
- CLI (
firecrawl) — preferred for simple, one-off tasks: quick scrapes, searches, site maps, piping output to other tools. Use it whenever a shell one-liner will do. - SDK (
@mendable/firecrawl-js) — use in TypeScript scripts when you need programmatic control, structured extraction with Zod schemas, or integration into larger workflows.
Steps
-
Install the CLI and authenticate via browser — This single command installs the CLI globally and opens the browser for Firecrawl authentication:
npx -y firecrawl-cli@latest init --agent cursor --browser--agent cursorinstalls the Firecrawl skill only for Cursor--browseropens the browser for authentication automatically
If the browser auth doesn't work, fall back to manual login:
npm install -g firecrawl-cli firecrawl login --browserOr if the user already has an API key (get one at firecrawl.dev/app/api-keys):
firecrawl login --api-key <their key>
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.
- 4d ago First seen · 167 lines · 0 tokens per session scan A 3fcd760623da
setup-firecrawl is a command published in the GitHub repository maccman/growth-agents (5 stars, last pushed 6mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,466 tokens. 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 commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.