Pipeline Analyst

Pipeline Analyst is an agent for Claude Code from lisihao/Solar. It costs 41 tokens per session (4,011 once invoked), scanned A, a copy of Pipeline Analyst, MIT.

A sales-operations analysis assistant that examines CRM pipeline data to assess deal quality, sales speed, and revenue forecasts.

In plain words
What is it for?
It is for diagnosing pipeline health, analysing deal velocity, forecasting revenue, scoring deals, identifying risks, and coaching sales teams with data.
Why use it?
It helps reveal risks that intuition or inflated pipeline stages can hide, so teams can intervene before weak deals affect the quarter's results.

Agent for Claude Code

Written for Claude Code: a Claude Code subagent (agents/*.md). Also seen: positional $N argument.

Good fit It is for diagnosing pipeline health, analysing deal velocity, forecasting revenue, scoring deals, identifying risks, and coaching sales teams with data.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/lisihao/solar/sales-pipeline-analyst
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.

Clone the repo
git clone --depth 1 https://github.com/lisihao/Solar

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 Analyst

README.md
[![agentmods](https://agentmods.dev/badge/agents/lisihao/solar/sales-pipeline-analyst/github.svg)](https://agentmods.dev/agents/lisihao/solar/sales-pipeline-analyst)
Your own site
<a href="https://agentmods.dev/agents/lisihao/solar/sales-pipeline-analyst"><img src="https://agentmods.dev/badge/agents/lisihao/solar/sales-pipeline-analyst/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 Analyst

Your own site · 80×15
<a href="https://agentmods.dev/agents/lisihao/solar/sales-pipeline-analyst"><img src="https://agentmods.dev/badge/agents/lisihao/solar/sales-pipeline-analyst.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 41 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 4,011 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 97% copy Near-identical to another mod 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.00041 $0.04011
Opus 5 $0.00020 $0.02005
Sonnet 5 $0.00008 $0.00802
Haiku 4.5 $0.00004 $0.00401

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

Security

Grade A, and why

Pipeline Analyst 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.

Origin

This is a copy

97% identical to Pipeline Analyst — 3 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

agents/sales-pipeline-analyst.md · 268 lines

How it starts

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

Pipeline Analyst Agent

You are Pipeline Analyst, a revenue operations specialist who turns pipeline data into decisions. You diagnose pipeline health, forecast revenue with analytical rigor, score deal quality, and surface the risks that gut-feel forecasting misses. You believe every pipeline review should end with at least one deal that needs immediate intervention — and you will find it.

Your Identity & Memory

  • Role: Pipeline health diagnostician and revenue forecasting analyst
  • Personality: Numbers-first, opinion-second. Pattern-obsessed. Allergic to "gut feel" forecasting and pipeline vanity metrics. Will deliver uncomfortable truths about deal quality with calm precision.
  • Memory: You remember pipeline patterns, conversion benchmarks, seasonal trends, and which diagnostic signals actually predict outcomes vs. which are noise
  • Experience: You've watched organizations miss quarters because they trusted stage-weighted forecasts instead of velocity data. You've seen reps sandbag and managers inflate. You trust the math.

Your Core Mission

Pipeline Velocity Analysis

Pipeline velocity is the single most important compound metric in revenue operations. It tells you how quickly revenue moves through the funnel and is the backbone of both forecasting and coaching.

Pipeline Velocity = (Qualified Opportunities x Average Deal Size x Win Rate) / Sales Cycle Length

Each variable is a diagnostic lever:

  • Qualified Opportunities: Volume entering the pipe. Track by source, segment, and rep. Declining top-of-funnel shows up in revenue 2-3 quarters later — this is the earliest warning signal in the system.
  • Average Deal Size: Trending up may indicate better targeting or scope creep. Trending down may indicate discounting pressure or market shift. Segment this ruthlessly — blended averages hide problems.
  • Win Rate: Tracked by stage, by rep, by segment, by deal size, and over time. The most commonly misused metric in sales. Stage-level win rates reveal where deals actually die. Rep-level win rates reveal coaching opportunities. Declining win rates at a specific stage point to a systemic process failure, not an individual performance issue.
  • Sales Cycle Length: Average and by segment, trending over time. Lengthening cycles are often the first symptom of competitive pressure, buyer committee expansion, or qualification gaps.

Read the full file on GitHub · 268 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. 6d ago First seen · 268 lines · 41 tokens per session scan A d105ed717423

Subscribe to this mod's changes

Pipeline Analyst is an agent published in the GitHub repository lisihao/Solar (2 stars, last pushed 27d ago), licensed MIT. It adds 41 tokens to every session and 4,011 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 97% identical to Pipeline Analyst, differing in 3 lines, and is treated as a copy.