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 skills/firecrawl/firecrawl-workflows/firecrawl-research-papersnpx skills add firecrawl/firecrawl-workflows --skill firecrawl-research-papersgit 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-research-papers)<a href="https://agentmods.dev/skills/firecrawl/firecrawl-workflows/firecrawl-research-papers"><img src="https://agentmods.dev/badge/skills/firecrawl/firecrawl-workflows/firecrawl-research-papers.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.1 | $0.00153 | $0.01611 |
| Opus 5 | $0.00077 | $0.00805 |
| Sonnet 5 | $0.00031 | $0.00322 |
| Haiku 4.5 | $0.00015 | $0.00161 |
Grade A, and why
firecrawl-research-papers 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 6d 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-research-papers — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 162 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Firecrawl Research Papers
Use this to create a sourced literature review.
Onboarding Interview
Infer the topic, source constraints, target count, and output format from context. If the topic is clear, proceed immediately.
Ask at most 1-3 concise questions only if blocked, such as the topic, target paper count, or required venue/date/method constraints.
Firecrawl Collection Plan
Use Firecrawl Research through the CLI, MCP, or equivalent Firecrawl tool surface as the primary path for paper discovery and verification. Fall back to general Firecrawl search and scrape for whitepapers, technical reports, research blogs, leaderboards, or facts outside the paper corpus.
What the paper index holds: paper abstracts, with full text reachable per paper. Its largest share is biomedical and life-science literature — PubMed journal articles plus bioRxiv and medRxiv preprints — so clinical, drug, gene, disease, epidemiology, and public-health questions are in scope. arXiv preprints cover computer science, physics, and mathematics. Coverage outside those sources is thinner, and the web tools below are the fallback there.
Core tools:
- MCP:
firecrawl_research_search_papers(query, k?)CLI:firecrawl research search-papers <query> [--k <number>]Semantic search over paper abstracts. Start here for most paper-finding queries, and retry with alternate framing when results are thin or too narrow. - MCP:
firecrawl_research_related_papers(seed_ids, intent, mode?, k?)CLI:firecrawl research related-papers <seedIds...> --intent <intent> [--mode <similar|citers|references>] [--k <number>]Expand from strong seed papers into similar work, citing papers, or references. Use this to find the relevant paper family, not just the first matching result. - MCP:
firecrawl_research_inspect_paper(id)CLI:firecrawl research inspect-paper <id>Fetch canonical metadata for a candidate paper: title, abstract, authors, categories, source ids, and dates. - MCP:
firecrawl_research_read_paper(id, question)CLI:firecrawl research read-paper <id> --question <question>Verify a specific claim or constraint inside one paper, such as method, reported score, benchmark, affiliation, comparison, or limitation. - MCP:
firecrawl_search(query)/firecrawl_scrape(url)CLI:firecrawl search <query>/firecrawl scrape <url>Use for web-only context: benchmark leaderboards, rankings, reports, whitepapers, research blogs, and source pages outside the paper index.
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.
- 6d ago First seen · 162 lines · 153 tokens per session scan A e93996e2209a
firecrawl-research-papers is a skill published in the GitHub repository firecrawl/firecrawl-workflows (151 stars, last pushed 15d ago), licensed ISC. It adds 153 tokens to every session and 1,611 once invoked, about $0.0008 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
hr-onboarding
A new-hire onboarding plan as a single page — first week schedule, buddy + manager intro, learning track, equipment checklist, and "you're set when…" outcomes. Use when the brief mentions "onboarding", "new hire", "first week plan", or "入职".
miniapp
Build a tiny interactive HTML playground only when someone asks to see, play with, or step through a mechanism.
eli5
Explain research, papers, or technical ideas in plain English with minimal jargon, concrete analogies, and clear takeaways. Use when the user says "ELI5 this", asks for a simple explanation of a paper or research result, wants jargon removed, or asks what something technically dense actually means.
deck-course-module
暖纸背景 + Playfair, 左侧学习目标常驻, 含 MCQ 自测页.
best-practices
Searchable knowledge base of 152+ programming best practices across 30+ languages and frameworks. BM25-powered search over curated resources from industry leaders (Google, Airbnb, Uber, Mozilla, Shopify, OWASP).
ark-documentation
Guidance for structuring Ark documentation using the Diataxis framework. Use this skill when creating new docs, deciding where content belongs, reviewing documentation PRs, or restructuring existing documentation.