firecrawl-dashboard-reporting

firecrawl-dashboard-reporting is a skill for Claude Code, Codex from firecrawl/firecrawl-workflows. It costs 48 tokens per session (511 once invoked), scanned A, original, ISC.

A workflow for reading visible metrics from analytics dashboards and internal web tools, including authenticated dashboards.

In plain words
What is it for?
Use it to extract KPI cards, tables, and dashboard sections, compare metrics across platforms, and produce a structured date-range report.
Why use it?
It gathers figures across dashboards and records their date range, units, sources, and limitations so the report is easier to verify.

Skill for Claude CodeCodex

Part of the firecrawl-workflows plugin — 16 skills shipped together

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.

agentmods
npx agentmods add skills/firecrawl/firecrawl-workflows/firecrawl-dashboard-reporting
Any agent
npx skills add firecrawl/firecrawl-workflows --skill firecrawl-dashboard-reporting
Clone the repo
git clone --depth 1 https://github.com/firecrawl/firecrawl-workflows

Made for: Claude Code, Codex.

Or install firecrawl-workflows, the plugin that ships this one along with the rest of its 16 skills.

Wrote 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.

agentmods badge for firecrawl-dashboard-reporting

README.md
[![agentmods](https://agentmods.dev/badge/skills/firecrawl/firecrawl-workflows/firecrawl-dashboard-reporting.svg)](https://agentmods.dev/skills/firecrawl/firecrawl-workflows/firecrawl-dashboard-reporting)
Your own site
<a href="https://agentmods.dev/skills/firecrawl/firecrawl-workflows/firecrawl-dashboard-reporting"><img src="https://agentmods.dev/badge/skills/firecrawl/firecrawl-workflows/firecrawl-dashboard-reporting.svg" alt="Measured on agentmods" height="20"></a>
Per session 48 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 511 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00048 $0.00511
Opus 5 $0.00024 $0.00255
Sonnet 5 $0.00010 $0.00102
Haiku 4.5 $0.00005 $0.00051

Measured 5d ago against content hash ab9605d85769, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-05, from the pricing page.

Security

Grade A, and why

firecrawl-dashboard-reporting 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 5d 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.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

skills/firecrawl-dashboard-reporting/SKILL.md · 76 lines

What it actually says

Firecrawl Dashboard Reporting

Use this to extract visible metrics from dashboards the user can legitimately access.

Onboarding Interview

Infer dashboard URLs, metrics, date range, and output format from context. If dashboard targets are clear and accessible, proceed immediately.

Ask at most 1-3 concise questions only if blocked, such as the dashboard URLs, auth/profile requirement, or date range.

Firecrawl Collection Plan

Use Firecrawl browser for authenticated dashboards and UI interaction:

  • open each dashboard
  • set or verify date range
  • extract visible KPI cards, tables, and labels
  • click tabs, expand sections, and scroll tables
  • use export/download buttons only when appropriate and allowed

If login has expired, ask the user to re-authenticate rather than attempting to bypass access controls.

Parallel Work

If appropriate, use sub-agents or equivalent parallel task runners. Split by dashboard platform or metric category. Each researcher should return metrics, units, period, source URL, and caveats.

Final Deliverable

# Dashboard Report

## Summary
[Highlights, alerts, trends]

## Metrics By Dashboard
[Platform, metric, value, unit, change, period]

## Tables Or Exports
[Captured tables/files and what they contain]

## Notes And Caveats
[Auth issues, chart-only data, unavailable metrics]

## Rerun Inputs
workflow: firecrawl-dashboard-reporting
dashboards: [urls]
date_range: [range]
metrics: [list]
output: [json/markdown]

JSON Shape

Use reportedAt, dateRange, dashboards[], metrics[], tables[], exports[], and summary.

Quality Bar

  • Extract actual numbers, not just chart labels.
  • Note when a chart cannot be read precisely.
  • Preserve date ranges and source URLs.
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. 5d ago First seen · 76 lines · 48 tokens per session scan A ab9605d85769

Subscribe to this mod's changes

firecrawl-dashboard-reporting is a skill published in the GitHub repository firecrawl/firecrawl-workflows (151 stars, last pushed 15d ago), licensed ISC. It adds 48 tokens to every session and 511 once invoked, about $0.0002 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.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

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…

microsoft/ai-agents-for-beginners · 200 tokens

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…

vercel/next.js · 95 tokens

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens

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…

vercel/next.js · 103 tokens

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…

microsoft/vscode · 72 tokens