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 deal-review-prepgit 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/deal-review-prep)<a href="https://agentmods.dev/skills/doris-labs/sales-skills/deal-review-prep"><img src="https://agentmods.dev/badge/skills/doris-labs/sales-skills/deal-review-prep/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/deal-review-prep"><img src="https://agentmods.dev/badge/skills/doris-labs/sales-skills/deal-review-prep.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.00081 | $0.01487 |
| Opus 5 | $0.00041 | $0.00744 |
| Sonnet 5 | $0.00016 | $0.00297 |
| Haiku 4.5 | $0.00008 | $0.00149 |
Grade A, and why
deal-review-prep 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 — 117 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Deal Review Prep
Purpose
Walk into a deal review or pipeline 1:1 with a tight story for each deal: where it stands, what moves it next, the one real risk, and the specific help you need. Make the manager's job confirming your plan — not extracting basics out of you.
Inputs
- The deal set under review (which deals, which scope — committed, best-case, or all open)
- Current stage, close date, and amount for each
- The next step on each deal and who owns it
- What you actually want from the manager (an intro, air cover, a discount, a resource)
Method
-
One-liner per deal. Force every deal into a single sentence the manager can absorb in five seconds:
<Account> — <stage>, <amount>, <close date>. Next: <next step + date>. Risk: <the one risk>. Ask: <specific help, or "none">.If you can't write it, you don't understand the deal — that's the finding. -
Anticipate the three probes. A good manager always presses on the same things. Have an evidence-backed answer ready for each:
- "Why this close date?" Tie it to a buyer-stated event or commitment (budget cycle, contract end, project kickoff), not to your quarter. "They said X by Y" beats "I think it'll land."
- "Who's the economic buyer, and have you met them?" Name the person, their role, and the date of last contact. "Champion only, EB unmet" is a valid honest answer — and itself becomes an ask.
- "What's the single biggest risk?" One risk, not five. Name it, say what you're doing about it, and what would prove it resolved.
-
Decide the ask before the meeting. For each deal, classify the help you need so the manager can act, not just nod:
- Access — exec sponsor intro, EB meeting, multi-thread support
- Authority — discount/term approval, non-standard contract sign-off
- Air cover — escalation, competitive pressure, "get our VP on a call"
- Resource — SE deep-dive, security review, proof-of-concept help
- None — explicitly say "on track, no help needed" so attention goes elsewhere
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 · 117 lines · 81 tokens per session scan A 8d966f346fc7
deal-review-prep is a skill published in the GitHub repository Doris-Labs/sales-skills (3 stars, last pushed 3mo ago), licensed MIT. It adds 81 tokens to every session and 1,487 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.