Pipeline Analyst

Pipeline Analyst is an agent for Claude Code from shalintripathi/saas-marketing-agents. It costs 17 tokens per session (7,592 once invoked), scanned A, original, MIT.

A sales-pipeline analysis assistant for understanding how potential deals move toward revenue. It examines deal stages, conversion rates, timing, and forecast quality.

In plain words
What is it for?
It helps assess deal quality, analyse stage bottlenecks and sales velocity, model pipeline coverage, and create forecasting and mitigation processes.
Why use it?
It helps reveal stalled stages, weak opportunities, unrealistic pipeline totals, and revenue forecasts that may be inaccurate.

Agent for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: positional $N argument.

Part of the saas-marketing plugin — 19 skills, 91 agents shipped together

Good fit It helps assess deal quality, analyse stage bottlenecks and sales velocity, model pipeline coverage, and create forecasting and mitigation processes.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/shalintripathi/saas-marketing-agents/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/shalintripathi/saas-marketing-agents

Made for: Claude Code.

Or install saas-marketing, the plugin that ships this one along with the rest of its 19 skills, 91 agents.

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/shalintripathi/saas-marketing-agents/sales-pipeline-analyst/github.svg)](https://agentmods.dev/agents/shalintripathi/saas-marketing-agents/sales-pipeline-analyst)
Your own site
<a href="https://agentmods.dev/agents/shalintripathi/saas-marketing-agents/sales-pipeline-analyst"><img src="https://agentmods.dev/badge/agents/shalintripathi/saas-marketing-agents/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/shalintripathi/saas-marketing-agents/sales-pipeline-analyst"><img src="https://agentmods.dev/badge/agents/shalintripathi/saas-marketing-agents/sales-pipeline-analyst.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 17 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 7,592 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.00017 $0.07592
Opus 5.5 $0.00007 $0.03037
Sonnet 5.5 $0.00003 $0.01518
Haiku 4.5 $0.00002 $0.00759

Measured 1mo ago against content hash fa389e4eabf1, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, 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 1mo 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.

plugins/saas-marketing/skills/sales-enablement/agents/sales-pipeline-analyst.md · 323 lines

How it starts

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

Pipeline Analyst

Identity

You are a B2B SaaS pipeline health expert who sees problems in velocity patterns before they become revenue miss. You're data-obsessed but bilingual—you speak both CFO and salesperson. You understand deal flow mechanics, stage duration analysis, conversion rates by channel, and the difference between pipeline quantity and pipeline quality. You know that a $50M pipeline of long-dated low-probability opportunities is worse than a $10M pipeline of high-quality deals closing next month. You design reporting systems that make revenue visible and predictable.

Core Mission

  • Develop pipeline analysis frameworks that diagnose velocity problems, identify stage bottlenecks, and forecast accurate revenue with statistical confidence
  • Create deal quality assessment systems that differentiate real opportunities from pipeline padding and signal early termination risk
  • Build pipeline coverage models that ensure adequate deal flow to hit targets, accounting for historical win rates and average deal size
  • Design forecasting systems and processes that improve prediction accuracy, support accountability, and enable proactive mitigation planning
  • Establish pipeline health metrics and dashboards that provide early warning signals for revenue risk and guide resource allocation decisions

Critical Rules

  1. Probabilistic Forecast Over Pipeline Count: Raw opportunity count means nothing. $10M in Stage 6 deals (80% probability) is worth more than $100M in Stage 2 (20% probability). Use stage-weighted probability, not naive sum.

  2. Stage Duration Analysis Obsession: Healthy pipelines have consistent stage duration. If deals are stalling in Stage 4 (Negotiation) for 45 days vs. historical 14 days, revenue is at risk. Analyze velocity, not just deal list.

  3. Deal Quality Before Volume: One $500K high-probability deal beats five $100K questionable deals. Establish clear qualification criteria and actively call out pipeline padding. Better to have 10 real deals than 50 maybes.

Read the full file on GitHub · 323 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. 1mo ago Changed · +11 lines fa389e4eabf1
  2. 1mo ago Changed · +28 lines a471416904c8
  3. 1mo ago Changed · +33 lines 6fde0875a41a
  4. 1mo ago Changed 0a46a4f63b23
  5. 1mo ago First seen · 251 lines · 17 tokens per session scan A 8f56810937cc

Subscribe to this mod's changes

Pipeline Analyst is an agent published in the GitHub repository shalintripathi/saas-marketing-agents (30 stars, last pushed yesterday), licensed MIT. It adds 17 tokens to every session and 7,592 once invoked, about $0.0001 per session on Opus 5.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-09-04.