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 Doris-Labs/sales-skills --skill pipeline-reviewgit clone --depth 1 https://github.com/Doris-Labs/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/doris-labs/sales-skills/pipeline-review)<a href="https://agentmods.dev/skills/doris-labs/sales-skills/pipeline-review"><img src="https://agentmods.dev/badge/skills/doris-labs/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/doris-labs/sales-skills/pipeline-review"><img src="https://agentmods.dev/badge/skills/doris-labs/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.00072 | $0.01797 |
| Opus 5 | $0.00036 | $0.00898 |
| Sonnet 5 | $0.00014 | $0.00359 |
| Haiku 4.5 | $0.00007 | $0.00180 |
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 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.
How it starts
The opening of the file, as written. The whole thing — 124 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pipeline Review
Purpose
Turn the full open pipeline into four artifacts: an honest coverage verdict against quota, a stage-distribution read (where deals are bunched and why that's a risk), an aging/stalled list, and a ranked "work this first" plan the AE can execute today.
Inputs
- The open pipeline: deal name, amount, stage, close date, last activity date, next step
- The quota/target for the period and how much is already closed-won (the gap)
- The period length (month/quarter) and average sales-cycle length, if known
Method
-
Coverage ratio. Sum open pipeline amount for deals closing in the period. Divide by the remaining gap (
quota − closed-won). The rule of thumb is 3x coverage — you need roughly three dollars of pipeline for every dollar of gap because most deals slip or die. Caveats that change the number:- 3x assumes a ~33% win rate. If your real win rate is 50%, 2x is fine; at 20%, you need 5x. Use your actual win rate, not the rule of thumb, whenever you have it.
- Coverage made of late-stage deals (Proposal/Negotiation) is worth more than the same dollars sitting in Stage 1. Report weighted coverage too: sum (amount × stage win rate). A 3x that's all early-stage is a red flag, not safety.
- Only count deals whose close date is actually inside the period. A 4x that's stuffed with deals closing next quarter is fake coverage.
-
Stage distribution. Bucket deal count and dollars by stage. Diagnose the shape:
- Too top-heavy (most deals/dollars in early stages): not enough has advanced; the period is at risk because nothing is close to landing. Action: qualify hard and kill or advance.
- Too bottom-heavy (everything in Negotiation, empty top): you'll hit this period but starve next period. Flag the dry top of funnel now.
- Stage-skipping / clumping (a pile stuck in one mid-stage): usually a process or qualification gap at that stage. Inspect those deals as a cohort.
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.
- 12d ago First seen · 124 lines · 72 tokens per session scan A f41faa04f1c6
pipeline-review is a skill published in the GitHub repository Doris-Labs/sales-skills (3 stars, last pushed 3mo ago), licensed MIT. It adds 72 tokens to every session and 1,797 once invoked, about $0.0004 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
lynqu
Entry point for the Lynqu sales suite — describe any sales situation and it composes the right skills across capture, outreach, quoting and reporting. Requires the Lynqu MCP server connected.
lynqu-sales-playbook
Turn a written sales playbook into a live Lynqu pipeline — contacts, timed tasks, follow-up templates, the playbook attached to each lead, and stage rules that deliver the prep at the right moment.
lynqu-card-studio
Create and update Lynqu digital business cards — contact info, social links, services, template, palette — and check card views, scans and shares. Requires the Lynqu MCP server connected.
lynqu-competitors
Build a battlecard for the incumbent on a Lynqu deal — switching cost, wedge, objections and honest answers — written back to the lead. Requires the Lynqu MCP server.
lynqu-contacts
Map the buying committee on an account — economic buyer, champion, blocker — and write it into Lynqu as contacts and participants. Requires the Lynqu MCP server.
lynqu-deal-desk
Price a Lynqu deal and draft the quote — browse the price book, put priced lines on a deal, then produce a draft quote for a human to send. Requires the Lynqu MCP server connected.