agentmods.dev

demo-deck

demo-deck is a command for Claude Code from bjorn-ingmanson/thefroject-plugins. It costs 0 tokens per session (358 once invoked), scanned A, original, MIT.

A command that creates a presentation tailored to a potential customer who has been assessed as a good fit.

In plain words
What is it for?
Use it to prepare sales demos and presentations based on a prospect's company, goals, decision-makers, budget, and discovery-call notes.
Why use it?
It organizes customer information, problems, evidence, pricing options, and next steps into a proposed presentation.

Command for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: reads .claude/ paths.

Part of the thefroject-customer-success plugin — 47 skills, 11 commands shipped together

not rated 1repo 4mo ago A scan 0 tokens original MIT

Good fit Use it to prepare sales demos and presentations based on a prospect's company, goals, decision-makers, budget, and discovery-call notes.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/bjorn-ingmanson/thefroject-plugins/demo-deck
View source ↗ bjorn-ingmanson/thefroject-plugins
Install

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.

Clone the repo
git clone --depth 1 https://github.com/bjorn-ingmanson/thefroject-plugins

Made for: Claude Code.

Or install thefroject-customer-success, the plugin that ships this one along with the rest of its 47 skills, 11 commands.

Wrote 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.

agentmods badge for demo-deck

README.md
[![agentmods](https://agentmods.dev/badge/commands/bjorn-ingmanson/thefroject-plugins/demo-deck/github.svg)](https://agentmods.dev/commands/bjorn-ingmanson/thefroject-plugins/demo-deck)
Your own site
<a href="https://agentmods.dev/commands/bjorn-ingmanson/thefroject-plugins/demo-deck"><img src="https://agentmods.dev/badge/commands/bjorn-ingmanson/thefroject-plugins/demo-deck/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.

agentmods 80×15 button for demo-deck

Your own site · 80×15
<a href="https://agentmods.dev/commands/bjorn-ingmanson/thefroject-plugins/demo-deck"><img src="https://agentmods.dev/badge/commands/bjorn-ingmanson/thefroject-plugins/demo-deck.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 358 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00000 $0.00358
Opus 5.5 $0.00000 $0.00143
Sonnet 5.5 $0.00000 $0.00072
Haiku 4.5 $0.00000 $0.00036

Measured 2mo ago against content hash 6f37228c6a74, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

demo-deck 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 2mo 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.

customer-success/commands/demo-deck.md · 32 lines

What it actually says

/demo-deck — Build Demo Deck

Build a tailored demo deck for a qualified prospect.

Before you start

Read these skill files if they exist (they define your voice and constraints):

  • .claude/skills/proposal-voice/ — copywriting rules for all client-facing docs
  • .claude/skills/pricing-guidelines/ — tiers, engagement models, pricing copy rules

Workflow

  1. Read context/business-info.md for your product positioning and ICP
  2. Gather prospect context:
    • Company name, industry, size
    • Key pain points or goals from the discovery call
    • Decision makers and their roles
    • Budget range or engagement tier (if known)
  3. Build the deck structure:
    • Title slide — Prospect name + your company, meeting date
    • Their world — 2-3 slides on their specific challenges (mirror their language)
    • The gap — What the current state costs them
    • The solution — Your approach mapped to their pain points
    • How it works — 3-5 slides showing the product/service in their context
    • Proof — Case study or metrics from a similar company
    • Investment — Engagement options (reference pricing-guidelines if available)
    • Next steps — Specific proposed actions with dates
  4. Save to outputs/decks/[company-name]-demo.md

Usage: /demo-deck [company name] [optional: notes from discovery call] Examples:

  • /demo-deck Acme Corp — they need help with pipeline automation
  • /demo-deck Northwind Traders — 50-person team, interested in enterprise tier
Changes

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.

  1. 2mo ago First seen · 32 lines · 0 tokens per session scan A 6f37228c6a74

Subscribe to this mod's changes

demo-deck is a command published in the GitHub repository bjorn-ingmanson/thefroject-plugins (1 stars, last pushed 4mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 358 tokens. 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.

Creative and mediaMarketing and SEO
Related

demo-deck compared with commands from other repositories

demo-deck next to 6 commands from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
demo-deckbjorn-ingmanson/thefroject-pluginsCommand14mo agoMITA0Claude Code
checklistgithub/spec-kitCommand148kyesterdayMITA13Claude Code
clarifygithub/spec-kitCommand148kyesterdayMITA27Claude Code
specifygithub/spec-kitCommand148kyesterdayMITA13Claude Code
analyzegithub/spec-kitCommand148kyesterdayMITA26Claude Code
convergegithub/spec-kitCommand148kyesterdayMITA35Claude Code
implementgithub/spec-kitCommand148kyesterdayMITA14Claude Code