Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/jbalbu01/sales-enablement-pluginnpx agentmods add commands/jbalbu01/sales-enablement-plugin/pipeline-digestWrote 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.
[](https://agentmods.dev/commands/jbalbu01/sales-enablement-plugin/pipeline-digest)<a href="https://agentmods.dev/commands/jbalbu01/sales-enablement-plugin/pipeline-digest"><img src="https://agentmods.dev/badge/commands/jbalbu01/sales-enablement-plugin/pipeline-digest/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.
<a href="https://agentmods.dev/commands/jbalbu01/sales-enablement-plugin/pipeline-digest"><img src="https://agentmods.dev/badge/commands/jbalbu01/sales-enablement-plugin/pipeline-digest.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00024 | $0.01613 |
| Opus 5 | $0.00012 | $0.00807 |
| Sonnet 5 | $0.00005 | $0.00323 |
| Haiku 4.5 | $0.00002 | $0.00161 |
Grade A, and why
pipeline-digest 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 9d 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.
How it starts
The opening of the file, as written. The whole thing — 184 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/pipeline-digest
If you see unfamiliar placeholders or need to check which tools are connected, see CONNECTORS.md.
Get a data-driven pipeline digest that goes beyond reporting into actionable intelligence. Designed for weekly team meetings, 1:1s, and forecast calls.
Usage
/pipeline-digest
/pipeline-digest enterprise team
/pipeline-digest Q2 forecast
Then provide pipeline data (upload CSV, paste from CRM, or describe your deals).
How It Works
┌─────────────────────────────────────────────────────────────────┐
│ PIPELINE DIGEST │
├─────────────────────────────────────────────────────────────────┤
│ STANDALONE (always works) │
│ ✓ Pipeline health assessment from provided data │
│ ✓ Stage conversion and velocity analysis │
│ ✓ Risk flagging based on deal pattern matching │
│ ✓ Coaching recommendations per rep │
│ ✓ Forecast scenarios (best / likely / worst) │
│ ✓ Recommended actions prioritized by impact │
├─────────────────────────────────────────────────────────────────┤
│ SUPERCHARGED (when you connect your tools) │
│ + CRM: Pull live pipeline data and deal history │
│ + Chat: Surface deal-related conversations and blockers │
│ + Calendar: Upcoming meetings that signal deal momentum │
│ + Transcription: Recent call insights per deal │
├─────────────────────────────────────────────────────────────────┤
│ LEARNING (compounds over time) │
│ → Reads from memory/deal-patterns.md for historical context │
│ → Reads rep-profile data to tailor coaching signals │
│ → Compares current patterns to past wins/losses │
│ → Updates memory/deal-patterns.md with new pattern observations │
│ → Tracks prediction accuracy to improve confidence scoring │
└─────────────────────────────────────────────────────────────────┘
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.
- 9d ago First seen · 184 lines · 24 tokens per session scan A ade34cb96f56
pipeline-digest is a command published in the GitHub repository jbalbu01/sales-enablement-plugin (14 stars, last pushed 6mo ago), licensed MIT. It adds 24 tokens to every session and 1,613 once invoked, about $0.0001 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.
Other commands, from other repositories
churn-prevention
Win/loss interview + churn analysis + retention playbook. Focuses on retention (not acquisition) — where 80% of the current plugin is focused. For B2B SaaS with churn > 5%/month, consulting with renewal rate < 70%, or a recurring business on a plateau.
audit
Offer diagnostic via the Value Equation — scores 1-10 on each vector (Dream Outcome, Probability, Time Delay, Effort), pinpoints the critical bottleneck, proposes the top 3 concrete levers, and rewrites the offer in 1 paragraph. Recommended prerequisite before LP and script.
client-onboarding
The client's first 30 days after the sale. A structured touch cadence, early quick wins to validate the purchase decision, visible value milestones. Cuts early churn (< 30 days) by a typical 40-60%. For consulting, agencies, cohort programs, mid-market B2B SaaS.
content-hub
30-90 day organic content roadmap. Topic × format × funnel stage × CTA. Healthy mix (60% educational, 25% entertainment, 15% promotional). For the founder/consultant who wants organic compounding over 6-18 months, not one viral post.
Email sequence (cold, warm, nurture, re-engagement). Generates 5-7 sequential emails with hook + agitation + proof + CTA, timing between touches, and context per touch. Tuned for B2B cold outreach — direct voice, no superlatives, specific proof.
help
Interactive decision matrix. Answer 3 questions and get the right command recommended. Useful for onboarding a new client or when you don't know where to start a session. Covers all 17 plugin commands.