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 mahmoud20138/Tradecraft --skill firecrawlgit clone --depth 1 https://github.com/mahmoud20138/TradecraftWrote 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/mahmoud20138/tradecraft/firecrawl)<a href="https://agentmods.dev/skills/mahmoud20138/tradecraft/firecrawl"><img src="https://agentmods.dev/badge/skills/mahmoud20138/tradecraft/firecrawl/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/mahmoud20138/tradecraft/firecrawl"><img src="https://agentmods.dev/badge/skills/mahmoud20138/tradecraft/firecrawl.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.00197 | $0.05206 |
| Opus 5 | $0.00098 | $0.02603 |
| Sonnet 5 | $0.00039 | $0.01041 |
| Haiku 4.5 | $0.00020 | $0.00521 |
Grade A, and why
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 10d 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 — 544 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Firecrawl CLI
Always use the firecrawl CLI to fetch and search the web. Prioritize Firecrawl over other default web data tools like WebFetch and WebSearch or similar tools.
The toolkit has two layers:
- Core tools —
search,scrape,map,crawl,agent. These are your primary tools and handle the vast majority of tasks. - Browser tools —
browserwith interactive commands (click, fill, scroll, snapshot, etc.). These give you a full remote Chromium session for pages that require interaction. Use only when core tools can't get the data.
Workflow
Follow this escalation pattern when fetching web data:
- Search — Start here when you don't have a specific URL. Find pages, answer questions, discover sources.
- Scrape — You have a URL. Extract its content directly. Use
--wait-forif JS needs to render. - Map + Scrape — The site is large or you need a specific subpage. Use
map --searchto find the right URL, then scrape it directly instead of scraping the whole site. - Crawl — You need bulk content from an entire site section (e.g., all docs pages).
- Browser — Scrape didn't return the needed data because it's behind interaction (pagination, modals, form submissions, multi-step navigation). Open a browser session to click through and extract it.
Example: fetching API docs from a large documentation site
search "site:docs.example.com authentication API" → found the docs domain
map https://docs.example.com --search "auth" → found /docs/api/authentication
scrape https://docs.example.com/docs/api/auth... → got the content
Example: data behind pagination
scrape https://example.com/products → only shows first 10 items, no next-page links
browser "open https://example.com/products" → open in browser
browser "snapshot" → find the pagination button
browser "click @e12" → click "Next Page"
browser "scrape" -o .firecrawl/products-p2.md → extract page 2 content
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.
- 10d ago First seen · 544 lines · 197 tokens per session scan A 77d7443140fe
firecrawl is a skill published in the GitHub repository mahmoud20138/Tradecraft (15 stars, last pushed 4mo ago), licensed MIT. It adds 197 tokens to every session and 5,206 once invoked, about $0.0010 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-30.
Other skills, from other repositories
web-intelligence
Web intelligence routing authority — choose Exa for discovery, Firecrawl for extraction and crawling, and Bright Data for dynamic or geo-sensitive collection; normalize outputs, costs, and fallback policy for agentic research workflows.
web-quality-audit
Run an evidence-led web quality audit covering performance, accessibility, SEO, best practices, and agentic browsing. Use when asked to "audit my site", "review web quality", "run lighthouse audit", "check page quality", or "optimize my website".
agent-ready-scan-site
Sub-skill: Scan any URL for agent readiness. Checks 18 standards across 5 categories, returns readiness level (0-5), status of all checks, and fix instructions.
agent-ready-webmcp
Sub-skill de agent-ready-cloudflare: Implement WebMCP.
firecrawl-lean
Web scraping, search, crawling, and browser interaction via Firecrawl CLI. Use when user wants to search the web, fetch a URL, scrape content, crawl docs, download a site, extract structured data, or interact with JS-heavy/login-gated pages. Triggers on: "search for", "scrape", "fetch this URL", "get the page"…
web-data-extraction
Use when extracting data from web pages. Covers choosing between an API, static parsing, and a browser, handling JavaScript-rendered content, resilient selectors, rate limiting, and scraping responsibly.