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 adam-lagerhausen/b2b-marketing-skills --skill demo-storylinegit clone --depth 1 https://github.com/adam-lagerhausen/b2b-marketing-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/adam-lagerhausen/b2b-marketing-skills/demo-storyline)<a href="https://agentmods.dev/skills/adam-lagerhausen/b2b-marketing-skills/demo-storyline"><img src="https://agentmods.dev/badge/skills/adam-lagerhausen/b2b-marketing-skills/demo-storyline/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/adam-lagerhausen/b2b-marketing-skills/demo-storyline"><img src="https://agentmods.dev/badge/skills/adam-lagerhausen/b2b-marketing-skills/demo-storyline.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.00041 | $0.01936 |
| Opus 5.5 | $0.00016 | $0.00774 |
| Sonnet 5.5 | $0.00008 | $0.00387 |
| Haiku 4.5 | $0.00004 | $0.00194 |
Grade A, and why
demo-storyline 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 1mo 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 — 203 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Demo Storyline
When to use
Use this skill when you need to plan a live or recorded B2B SaaS demo that advances a sales conversation.
Best fit for:
- First-call product demos
- Discovery-led demos after an initial qualification conversation
- Founder-led demos that need to become repeatable
- AE or SE demo talk tracks
- Custom interactive demos for a target segment or account
- Demo sections inside sales narrative decks
- Demo prep for vertical, persona, or use-case-specific sales motions
Do not use this skill to create a feature tour, product training script, help documentation, or generic click path. A strong demo should map to buyer pain, not inventory the product.
Inputs
Ask for or infer as much of the following as possible:
- Target audience: buyer, practitioner, economic buyer, technical evaluator, industry, company size
- Buyer pain: what is broken, slow, expensive, risky, confusing, or newly urgent
- Current workflow: spreadsheets, legacy tools, manual process, services, internal workaround, competitor
- Desired outcome: what the buyer wants to improve, avoid, prove, or make easier
- Product area: the specific workflow, capability, or use case to demo
- Sales stage: first call, deep discovery, technical validation, executive demo, renewal, expansion
- Qualification goal: what the rep needs to learn or confirm during the demo
- Demo environment: available screens, data, integrations, personas, records, and constraints
- Realistic data: company names, user roles, customer records, pipeline values, dates, tasks, metrics, statuses
- Proof: customer story, metric, quote, benchmark, or before/after result
- Objections or likely confusion: implementation, integrations, data quality, security, adoption, ROI, differentiation
- Next step: stakeholder meeting, pilot, mutual action plan, technical validation, business case, proposal
If inputs are thin, produce a useful draft with explicit assumptions and gaps. Never fill the demo with generic placeholders like "Item 1," "Customer A," or "Task 2" when realistic examples can be invented or requested.
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.
- 1mo ago First seen · 203 lines · 41 tokens per session scan A d66521621eba
demo-storyline is a skill published in the GitHub repository adam-lagerhausen/b2b-marketing-skills (6 stars, last pushed 4mo ago), licensed MIT. It adds 41 tokens to every session and 1,936 once invoked, about $0.0002 per session on Opus 5.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
go-to-market-playbook
A reusable Go-to-Market strategy template for both B2B and B2C launches. Covers positioning, messaging, ICP definition, channel selection, and competitive analysis frameworks. By @WeiYipei.
skill-catalog
Maintains the central registry of all skills with dependencies, trigger phrases, review gates, and chaining.
gbp-review-strategy
Analyzes review velocity, sentiment distribution, and competitor review patterns, then produces branded response.
design-reviewer
Reviews implemented React/Tailwind/CSS output for design quality across 5 dimensions scored 0-4: anti-patterns.
design-incident-response
Triage decision tree for design incidents flagged by /design-reviewer.
learn
Process raw source material (transcripts, docs, articles, competitor pages, meeting notes) into structured context.