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 customer-story-enginegit 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/customer-story-engine)<a href="https://agentmods.dev/skills/adam-lagerhausen/b2b-marketing-skills/customer-story-engine"><img src="https://agentmods.dev/badge/skills/adam-lagerhausen/b2b-marketing-skills/customer-story-engine/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/customer-story-engine"><img src="https://agentmods.dev/badge/skills/adam-lagerhausen/b2b-marketing-skills/customer-story-engine.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.00038 | $0.02226 |
| Opus 5 | $0.00019 | $0.01113 |
| Sonnet 5 | $0.00008 | $0.00445 |
| Haiku 4.5 | $0.00004 | $0.00223 |
Grade A, and why
customer-story-engine 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 — 298 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Customer Story Engine
When to use
Use this skill when you need to turn a customer sale, renewal, implementation, interview, support note, or founder/sales anecdote into a credible customer story.
Use it for:
- Capturing a story after every sale or meaningful customer outcome
- Turning past customer notes into usable proof
- Preparing customer interview questions
- Creating a website customer story
- Creating a one-page customer-story PDF for sales
- Building sales proof from true before/after examples
- Finding better messaging from real customer situations
Core belief: stories sell better than claims. A customer story beats twenty product pages when it shows a real person facing a real problem, making a change, and getting a tangible result.
ADI Marketing principle: "We tell true stories to the right people at the right time."
Inputs
Ask for or infer the following:
- Company, product, or service being sold
- Customer type, role, and situation
- The old make-do process before buying
- The trigger: the specific event that made them call, act, or finally decide
- What the product or service changed
- The tangible result: money saved, flight saved, fuel sale protected, time saved, risk reduced, peace of mind, or another real outcome
- Direct customer quotes or plain-language notes
- What can and cannot be claimed publicly
- Customer permission status, if known
- Desired output: story brief, case study, one-pager, website post, sales proof, or interview guide
If proof is thin, still create the story structure, but label gaps clearly. Do not invent numbers, quotes, outcomes, logos, names, timelines, or customer permission.
Story capture questions
Use these questions in an interview, follow-up email, sales handoff, or internal debrief.
1. Situation: what was happening before?
- What was the old way of doing this?
- What tools, spreadsheets, calls, texts, sticky notes, manual steps, or workarounds were involved?
- Who had to coordinate the work?
- What usually went fine?
- Where did the old way get messy, slow, risky, expensive, or stressful?
- What did the customer tolerate because it was familiar?
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 · 298 lines · 38 tokens per session scan A cf932e51836c
customer-story-engine is a skill published in the GitHub repository adam-lagerhausen/b2b-marketing-skills (5 stars, last pushed 2mo ago), licensed MIT. It adds 38 tokens to every session and 2,226 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-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.
adoption-leaderboard
Scores a rep's or a team's recent sales calls against a fixed set of five winning-behavior checklists (rapport, upsell signals, renewal risk, customer experience, value realization), then ranks reps lowest-adoption-first so the highest-leverage coaching targets lead. Use when running a team calibration, prepping 1:1…
challenger
Audits a B2B sales call transcript against the Challenger Sale framework (teach, tailor, take control, plus the commercial-teaching pitch arc), or sweeps a CRM export for deals with no teaching insight logged. Use when a rep leans on discovery-question skill but rarely brings a point of view, when prepping a rep for a…
champion-tracker
Tracks champion strength across a deal's call(s) — builds an action ledger, one row per named contact per cited quote, tagging each as either an act of internal selling (looping in a stakeholder, pushing back for the rep in a room the rep wasn't in) or mere positive sentiment (encouraging words, no action), then reads…
end-client-registration
Audits a partner/reseller's end-client deal registration for completeness — partner identity, end-client entity kept distinct from the partner, engagement scope, conflict check against the direct pipeline, confirmed permission to engage the end-client contact, commercial terms, and an expiry window. Use when reviewing…
executive-briefing
Writes the short brief a rep sends upward out of one deal — to their own exec or the buyer's exec sponsor — covering deal snapshot, status, what's at risk, and the ask, each claim cited to a quote or a CSV column/cell. Use when someone who will never read the transcript needs to act on one deal, not a call-by-call…