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 The-AI-Directory-Company/agents-and-skills --skill sales-demo-scriptgit clone --depth 1 https://github.com/The-AI-Directory-Company/agents-and-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/the-ai-directory-company/agents-and-skills/sales-demo-script)<a href="https://agentmods.dev/skills/the-ai-directory-company/agents-and-skills/sales-demo-script"><img src="https://agentmods.dev/badge/skills/the-ai-directory-company/agents-and-skills/sales-demo-script/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/the-ai-directory-company/agents-and-skills/sales-demo-script"><img src="https://agentmods.dev/badge/skills/the-ai-directory-company/agents-and-skills/sales-demo-script.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.00034 | $0.01444 |
| Opus 5 | $0.00017 | $0.00722 |
| Sonnet 5 | $0.00007 | $0.00289 |
| Haiku 4.5 | $0.00003 | $0.00144 |
Grade A, and why
sales-demo-script 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 8d 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 — 137 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Sales Demo Script
Before you start
Gather the following from the user. If anything is missing, ask before proceeding:
- What product or feature are you demoing? (Full product, specific module, new capability)
- Who is the audience? (Job title, technical depth, decision-making authority)
- What problem does the audience care about? (In their language, not your feature names)
- What is the current alternative? (Competitor, manual process, internal tool)
- What are the top 3 objections you hear? (Price, switching cost, security, "build it ourselves")
- What is the desired next step? (Free trial, POC, procurement, technical deep-dive)
- How long is the demo slot? (15, 30, or 45 minutes — determines scope)
Demo script template
1. Opening (2-3 minutes)
Set context before touching the product.
"Before I show you anything — from our conversation, I understand
[specific pain point]. You're using [current process/tool] and the
main challenge is [consequence]. Still accurate?"
"I'll show you three things:
1. How [product] handles [pain point 1]
2. How it compares to [alternative] for [pain point 2]
3. [Unique differentiator]
Then we'll talk next steps."
Always confirm the problem before demoing. If the audience corrects you, adapt on the spot.
2. Discovery Questions (3-5 minutes)
If discovery was not done in a prior call, embed these before the walkthrough:
- Current state: "Walk me through how your team handles [process] today."
- Pain: "What breaks first when volume increases?"
- Impact: "When [problem] happens, what does that cost in time/revenue?"
- Decision criteria: "What would success look like in the first 30 days?"
- Stakeholders: "Who else would need to evaluate this?"
- Timeline: "Is there a deadline driving the timing?"
Listen more than you talk. Answers determine which features to emphasize and which to skip.
3. Product Walkthrough (15-25 minutes)
Structure the walkthrough as a story, not a feature tour. Each section follows the pattern: Problem > Solution > Proof.
What ships with it
3 files 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.
- 8d ago First seen · 137 lines · 34 tokens per session scan A 9d7611065189
sales-demo-script is a skill published in the GitHub repository The-AI-Directory-Company/agents-and-skills (2 stars, last pushed 5mo ago), licensed MIT. It adds 34 tokens to every session and 1,444 once invoked, about $0.0002 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-09-03.
Other skills, from other repositories
writing-workflow-skills
Use when adding a new workflow skill to pi-thinkrail-workflow, changing an existing workflow skill's role, trigger, handoff, or structure, or checking a workflow skill against the workflow system's rules. Not for authoring general-purpose skills outside this package.
case-interview-practice
Interactive consulting case interview practice with structured frameworks, feedback mechanisms, and progressive difficulty. Use when preparing for management consulting interviews, case competitions, or business problem-solving exercises.
i18n-localization
Internationalization and localization for global applications. Use when adding multi-language support, handling regional formats, or preparing apps for global markets.
electron-desktop
Desktop application development with Electron for Windows, macOS, and Linux. Use when building cross-platform desktop apps, implementing native OS features, or packaging web apps for desktop.
finance
Financial analysis expertise for financial modeling (DCF, LBO, M&A), valuation, financial statement analysis, capital allocation, treasury management, and corporate finance decisions. Use when building financial models, analyzing statements, or making investment decisions.
investment-memo-generator
Investment memo creation combining financial analysis, document generation, and structured templates. Use when creating investment memos, pitch decks, deal summaries, or investment committee materials.