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 executive-briefinggit 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/executive-briefing)<a href="https://agentmods.dev/skills/doris-labs/sales-skills/executive-briefing"><img src="https://agentmods.dev/badge/skills/doris-labs/sales-skills/executive-briefing/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/executive-briefing"><img src="https://agentmods.dev/badge/skills/doris-labs/sales-skills/executive-briefing.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.00086 | $0.01309 |
| Opus 5 | $0.00043 | $0.00655 |
| Sonnet 5 | $0.00017 | $0.00262 |
| Haiku 4.5 | $0.00009 | $0.00131 |
Grade A, and why
executive-briefing 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 — 105 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Executive Briefing
Purpose
Compress a deal into a one-page executive brief that lands the "so what" in the first two lines. Execs don't read activity logs — they read outcomes, impact, and the ask. This skill produces a brief that respects 60 seconds of attention.
Inputs
- The deal: account, size, stage, close date
- The outcome you want from the reader (approval, escalation, awareness, a decision)
- Who the reader is and their lens (CFO, CEO, CRO, your VP, customer sponsor)
- The business impact in numbers (ARR, time-to-value, cost avoided, risk)
Method
- Lead with the "so what." First line states the outcome and your recommendation, not background. The exec should know what you want before line three. If they read nothing else, the top two lines must stand alone.
- Outcome and recommendation first. State where the deal lands and what you're asking the reader to do. Background and narrative come after the bottom line.
- Quantify impact over activity. "$240K ARR, 6-week deployment, replaces two incumbent tools" beats "had a great demo, strong champion." Every claim carries a number or a named consequence. No adjectives doing a number's job.
- Make the ask explicit and single. One clear request — an approval, an intro, a discount sign-off, an escalation. State who must do what by when.
- Surface risks honestly, with mitigation. Two or three real risks, each paired with what you're doing about it. Execs distrust briefs with no risks.
- Tailor to the reader's lens:
- CFO — money and certainty. Lead with ARR, payback period, cost displaced, contract term, discount exposure, forecast confidence. Frame risk as financial.
- CEO — strategic narrative. Lead with market signal, logo value, competitive displacement, what this deal proves. Keep numbers, drop the line items.
- CRO / VP Sales — forecast and execution. Lead with stage, commit category, close date confidence, what's blocking, and what you need to land it this quarter.
- Ruthless brevity. One page, ~150 words of prose plus the structured block. Cut anything that doesn't change the reader's decision. If a sentence doesn't move the ask, delete it.
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 · 105 lines · 86 tokens per session scan A 0f0cb611179b
executive-briefing is a skill published in the GitHub repository Doris-Labs/sales-skills (3 stars, last pushed 3mo ago), licensed MIT. It adds 86 tokens to every session and 1,309 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.