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.
/plugin marketplace add firecrawl/firecrawl-workflowsnpx agentmods add plugins/firecrawl/firecrawl-workflows/firecrawl-workflowsgit clone --depth 1 https://github.com/firecrawl/firecrawl-workflowsGrade 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.
What it actually says
{
"name": "firecrawl-workflows",
"displayName": "Firecrawl Workflows",
"description": "Outcome-focused Firecrawl workflow skills for research, SEO audits, QA, knowledge bases, lead lists, dashboard reporting, shopping, and design-system extraction.",
"version": "0.1.0",
"author": {
"name": "Firecrawl",
"url": "https://www.firecrawl.dev"
},
"homepage": "https://www.firecrawl.dev",
"repository": "https://github.com/firecrawl/firecrawl-workflows",
"license": "ISC",
"keywords": ["firecrawl", "workflows", "research", "seo", "qa", "knowledge-base", "lead-gen", "design-system"],
"skills": [
"./skills/firecrawl-workflows",
"./skills/firecrawl-website-design-clone",
"./skills/firecrawl-deep-research",
"./skills/firecrawl-seo-audit",
"./skills/firecrawl-lead-research",
"./skills/firecrawl-qa",
"./skills/firecrawl-competitive-intel",
"./skills/firecrawl-company-directories",
"./skills/firecrawl-dashboard-reporting",
"./skills/firecrawl-knowledge-base",
"./skills/firecrawl-knowledge-ingest",
"./skills/firecrawl-lead-gen",
"./skills/firecrawl-market-research",
"./skills/firecrawl-research-papers",
"./skills/firecrawl-demo-walkthrough",
"./skills/firecrawl-shop"
]
}
What ships with it
1 file beside plugin.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.
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.
- yesterday First seen · 33 lines scan A 8ef99bd1084a
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.
Other plugins, from other repositories
nextjs
Official Next.js skills: adopt and optimize Cache Components, adopt Partial Prefetching, and verify runtime behavior against a running dev server.
nextjs
Official Claude Code plugin marketplace for Next.js, serving the skills that ship in the vercel/next.js repository.
claude-plugins-official
Directory of popular Claude Code extensions including development tools, productivity plugins, and MCP integrations.
knowledge-work-plugins
Plugin marketplace listing 97 plugins: noibu, productivity, enterprise-search, cowork-plugin-management, sales.
ecc
Plugin marketplace listing 1 plugin: ecc.
ecc
Harness-native ECC plugin for engineering teams - 68 agents, 286 skills, 94 legacy command shims, reusable hooks, rules, MCP conventions, and operator workflows for Claude Code plus adjacent agent harnesses.