full-funnel-ai-analytics: Command for Claude Code

.claude/commands/pipeline.md

pipeline is a command for Claude Code from eduardocornelsen/full-funnel-ai-analytics. It costs 0 tokens per session (598 once invoked), scanned A, original, MIT.

A command for creating a sales pipeline dashboard, which shows how potential deals move through stages before becoming sales.

In plain words
What is it for?
Use it to display pipeline value, deal sizes, win rate, active deals, forecasts, and stage-by-stage progress in a React chart.
Why use it?
It keeps dashboard figures tied to the approved data file and prevents mixing lifetime customer data with results from a recent 90-day period.

Command for Claude Code

Written for Claude Code: installed under .claude/. Also seen: mentions CLAUDE.md.

This is eduardocornelsen/full-funnel-ai-analytics's own configuration. It tells Claude Code how to work on full-funnel-ai-analytics itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything full-funnel-ai-analytics configures →

Reuse

Borrowing it

Nothing to install: this file belongs to eduardocornelsen/full-funnel-ai-analytics. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/eduardocornelsen/full-funnel-ai-analytics/main/.claude/commands/pipeline.md
Clone the repo
git clone --depth 1 https://github.com/eduardocornelsen/full-funnel-ai-analytics

Made for: Claude Code.

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 pipeline

README.md
[![agentmods](https://agentmods.dev/badge/commands/eduardocornelsen/full-funnel-ai-analytics/pipeline/github.svg)](https://agentmods.dev/commands/eduardocornelsen/full-funnel-ai-analytics/pipeline)
Your own site
<a href="https://agentmods.dev/commands/eduardocornelsen/full-funnel-ai-analytics/pipeline"><img src="https://agentmods.dev/badge/commands/eduardocornelsen/full-funnel-ai-analytics/pipeline/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for pipeline

Your own site · 80×15
<a href="https://agentmods.dev/commands/eduardocornelsen/full-funnel-ai-analytics/pipeline"><img src="https://agentmods.dev/badge/commands/eduardocornelsen/full-funnel-ai-analytics/pipeline.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 598 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.00000 $0.00598
Opus 5 $0.00000 $0.00299
Sonnet 5 $0.00000 $0.00120
Haiku 4.5 $0.00000 $0.00060

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

Security

Grade A, and why

pipeline 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 12d 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.

.claude/commands/pipeline.md · 26 lines

How it starts

The opening of the file, as written. The whole thing — 26 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Data sourcing (mandatory)

Read dashboards/golden_metrics.jsonall_time.crm (HubSpot + Salesforce) and copy exact values — never recalculate (CLAUDE.md §14).

  • All CRM figures are lifetime — label every KPI CRM all-time (§2); never mix with 90-day attributed revenue (§3).
  • Win rate = closed_won / (closed_won + closed_lost) (§1).
  • Freshness badge in the header: Data as of _meta.generated_at · CRM all-time scope.

Live MCP variant — only if the user appends -mcp or asks for "live" / "real-time" / "raw platform" data: query the hubspot, salesforce MCP servers instead, passing dates from _meta.window_start / _meta.window_end, add the badge ⚡ Live MCP — may differ from golden layer, and use dashboards/js/metrics.js canonical formulas for any computed metric.

Artifact

Build a sales pipeline React artifact using Recharts.

Design: dark theme (#0d0d1a bg, #1a1a2e cards), green #34d399, blue #60a5fa, amber #fbbf24, coral #f87171.

Include these 7 sections:

  1. Pipeline KPI cards — Total Pipeline Value, Avg Deal Size, Win Rate, Deals in Progress, Forecasted Revenue
  2. Stage progression funnel — horizontal funnel chart showing deal count and value at each stage (HubSpot + Salesforce merged)
  3. Revenue by lead source — horizontal bar chart from Salesforce closed-won data
  4. Velocity gauge — a simple visual showing average days in pipeline vs target (use a progress arc)
  5. Deal age heatmap — table of stages vs age buckets (0-30d, 31-60d, 61-90d, 90d+) with color intensity
  6. Contacts by lifecycle — donut chart of HubSpot lifecycle stages
  7. AI Insights panel — a dark card at the bottom with a "✦ AI Insights" header containing 4–5 bullet points synthesized across HubSpot and Salesforce data. Each bullet must be specific, quantified, and actionable. Cover: (a) the stage with the biggest conversion drop-off and what it signals about the sales process, (b) pipeline velocity vs target — whether the team is on track and what is causing lag if not, (c) the lead source generating the highest-value closed-won deals and whether it is being prioritized, (d) any deal age concentration risk (large value stuck in late stages for too long), (e) a forecast accuracy observation — how weighted pipeline compares to closed-won run rate. Write in plain English as if briefing a sales leader or VP of Revenue.

Read the full file on GitHub · 26 lines

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. 12d ago First seen · 26 lines · 0 tokens per session scan A ef5693fc93ea

Subscribe to this mod's changes

pipeline is a command published in the GitHub repository eduardocornelsen/full-funnel-ai-analytics (21 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 598 tokens. 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.