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 firecrawl/firecrawl-workflows --skill firecrawl-lead-researchgit clone --depth 1 https://github.com/firecrawl/firecrawl-workflowsWrote 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/firecrawl/firecrawl-workflows/firecrawl-lead-research)<a href="https://agentmods.dev/skills/firecrawl/firecrawl-workflows/firecrawl-lead-research"><img src="https://agentmods.dev/badge/skills/firecrawl/firecrawl-workflows/firecrawl-lead-research.svg" alt="Measured on agentmods" height="20"></a>- Socket pass
- Snyk warn
- NVIDIA SkillSpector pass
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.00056 | $0.00501 |
| Opus 5 | $0.00028 | $0.00251 |
| Sonnet 5 | $0.00011 | $0.00100 |
| Haiku 4.5 | $0.00006 | $0.00050 |
Grade A, and why
firecrawl-lead-research 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 8d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- firecrawl-lead-research — 100% identical, 0 lines differ
What it actually says
Firecrawl Lead Research
Use this to create a concise, actionable pre-meeting brief.
Onboarding Interview
Infer the company, person, meeting context, and desired brief depth from context. If the company is clear, proceed immediately.
Ask at most 1-3 concise questions only if blocked, such as the company/person to research or the meeting context.
Firecrawl Collection Plan
Use Firecrawl search and scrape to gather:
- company website, about, product, pricing, careers, team, and customer pages
- recent news, funding, launches, hiring, partnerships, and press
- public person profiles, talks, posts, interviews, and role/background
- relevant industry context and likely business challenges
Parallel Work
If appropriate, use sub-agents or equivalent parallel task runners:
- Company Profile researcher
- Recent News and Activity researcher
- Person researcher
- Industry/Pain Point researcher
Each researcher should return source URLs and only evidence-backed claims.
Final Deliverable
# Lead Brief: [Company]
## Company Overview
[What they do, stage/size signals, products, customers]
## Recent Activity
[News, launches, funding, hiring, partnerships]
## Key People
[Relevant people and public background]
## Talking Points
[5-7 specific conversation starters]
## Likely Pain Points
[Evidence-backed hypotheses]
## Outreach Angle
[Suggested positioning or next step]
## Sources
[URLs used]
## Rerun Inputs
workflow: firecrawl-lead-research
company: [name/url]
person: [optional]
context: [meeting context]
Quality Bar
- Keep it concise and useful before a meeting.
- Do not fabricate personal details.
- Clearly separate facts from inferred pain points.
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.
- 8d ago First seen · 84 lines · 56 tokens per session scan A 1b52c42404c5
firecrawl-lead-research is a skill published in the GitHub repository firecrawl/firecrawl-workflows (154 stars, last pushed 17d ago), licensed ISC. It adds 56 tokens to every session and 501 once invoked, about $0.0003 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…