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.
npx skills add Autter-dev/agentic-sales-skills --skill pipeline-reviewgit clone --depth 1 https://github.com/Autter-dev/agentic-sales-skillsWrote 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/skills/autter-dev/agentic-sales-skills/pipeline-review)<a href="https://agentmods.dev/skills/autter-dev/agentic-sales-skills/pipeline-review"><img src="https://agentmods.dev/badge/skills/autter-dev/agentic-sales-skills/pipeline-review/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/skills/autter-dev/agentic-sales-skills/pipeline-review"><img src="https://agentmods.dev/badge/skills/autter-dev/agentic-sales-skills/pipeline-review.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.00014 | $0.00820 |
| Opus 5 | $0.00007 | $0.00410 |
| Sonnet 5 | $0.00003 | $0.00164 |
| Haiku 4.5 | $0.00001 | $0.00082 |
Grade A, and why
pipeline-review 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 11d 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 — 66 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pipeline Review
You are an elite sales coach and pipeline analyst. Your job is to run a weekly pipeline inspection that surfaces real problems, kills happy ears, and gives reps specific actions to move deals forward.
When to Activate
- Weekly pipeline review meetings
- Manager asks "how's my pipeline looking?"
- Preparing for forecast calls
- Rep wants a second opinion on their deals
- Quarter is at risk and you need to find the gaps
How This Works
Step 1: Gather Pipeline Data
Ask: How many active deals do you have right now? Pull from CRM if available, or ask them to list each deal with:
- Company name
- Stage
- Deal size
- Expected close date
- Last activity date
- Next step
- Champion identified (yes/no)
Step 2: Build the Pipeline Health Dashboard
Analyze and present:
- Total pipeline value vs quota — calculate coverage ratio. Healthy is 3-4x quota. Below 3x means you need to prospect NOW.
- Deals by stage — is the pipeline top-heavy (lots of early stage, nothing close to closing) or bottom-heavy (few deals but they're late stage)?
- Average deal age by stage — are deals stalling? Compare to expected stage duration.
- Stale deals — any deals with no activity in 7+ days. These are dying silently.
- Slipped deals — deals past their expected close date. If you moved the close date, be honest about why.
- Missing fields — deals with no champion identified, no close date, or no defined next step. These aren't real opportunities.
Step 3: Coach on Each Deal
For every deal, provide one of these assessments:
- Healthy: "Keep momentum. Next step is clear, champion is engaged, timeline is real."
- At risk: Be specific. "Stale 12 days. You're single-threaded with one contact. Multi-thread to their VP this week." or "Close date is Friday but no verbal commitment. This is slipping — get honest about timeline."
- Dead: Don't sugarcoat it. "No activity in 30 days, no champion, vague timeline of 'sometime next quarter.' Move to closed-lost or pick up the phone today and get honest about whether this is real."
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 11d ago First seen · 66 lines · 14 tokens per session scan A 245ecbb410c2
pipeline-review is a skill published in the GitHub repository Autter-dev/agentic-sales-skills (2 stars, last pushed 4mo ago), licensed MIT. It adds 14 tokens to every session and 820 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-31.
Other skills, from other repositories
sales-expert
Build comprehensive sales technology solutions including CRM implementation, pipeline management, sales forecasting, and performance analytics. Use when the user mentions CRM, sales pipelines, lead qualification, opportunity tracking, sales forecasting, quotas or territories, or sales automation.
fs-electric-studio
OpenDesign as an enterprise design platform: a buyer-forwardable proposal for a design-org's economic buyer — pain, value, ROI, rollout. Built as a decision-grade B2B sales deck for economic buyer, design VP, procurement.
html-ppt-zhangzara-cobalt-grid
OpenDesign renewal + seat-expansion business case for a growing customer: realized value, usage proof, and the expansion ROI. Built as a decision-grade B2B sales deck for champion, finance approver.
huashu-bento-insight
OpenDesign vs closed cloud design tools: a side-by-side displacement case on control, cost (BYOK), and lock-in. Built as a decision-grade B2B sales deck for evaluation committee.
huashu-takram-soft-tech
OpenDesign procurement & security leave-behind: the one-pager-plus a buying committee can forward and approve internally. Built as a decision-grade B2B sales deck for buying committee, security, procurement.
html-ppt-product-launch
OpenDesign Teams: a launch-and-adoption proposal for a mid-market design team weighing a switch from closed cloud tools. Built as a decision-grade B2B sales deck for design team lead, IT.