firecrawl-workflows

A plugin catalogue entry for firecrawl-workflows, a collection of workflows for web research, SEO checks, quality assurance, knowledge bases, lead lists, dashboards, shopping research, and extracting design systems.

In plain words
What is it for?
Use it as a catalogue description when presenting the firecrawl-workflows plugin. The supplied information only supports these listed workflow areas, not specific commands or outputs.
Why use it?
It tells a catalogue reader what the plugin contains and which broad jobs it covers. The entry itself provides no details about how those workflows work.

Plugin for Claude Code

Install

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.

Claude Code
/plugin marketplace add firecrawl/firecrawl-workflows
agentmods
npx agentmods add plugins/firecrawl/firecrawl-workflows/marketplace
Clone the repo
git clone --depth 1 https://github.com/firecrawl/firecrawl-workflows

Made for: Claude Code.

Per session not measured What this adds to a session before it is invoked.
When invoked not measured Not applicable: nothing here is loaded into a session.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Security

Grade A, and why

firecrawl-workflows 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.

.claude-plugin/marketplace.json · 15 lines

What it actually says

{
  "name": "firecrawl-workflows",
  "owner": {
    "name": "Firecrawl",
    "email": "[email protected]"
  },
  "plugins": [
    {
      "name": "firecrawl-workflows",
      "source": "./",
      "description": "Outcome-focused Firecrawl workflow skills for research, SEO audits, QA, knowledge bases, lead lists, dashboard reporting, shopping, and design-system extraction."
    }
  ]
}
Files

What ships with it

1 file beside marketplace.json in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

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.

  1. yesterday First seen · 15 lines scan A df9864ec7bf6

Subscribe to this mod's changes

firecrawl-workflows is a plugin published in the GitHub repository firecrawl/firecrawl-workflows (145 stars, last pushed 11d ago), licensed ISC. Its token cost is not measured: this kind of file is read by the harness, not the model. 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.