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 mardab96/b2b-lead-generation-claude-skills --skill ghosted-after-the-demogit clone --depth 1 https://github.com/mardab96/b2b-lead-generation-claude-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/mardab96/b2b-lead-generation-claude-skills/ghosted-after-the-demo)<a href="https://agentmods.dev/skills/mardab96/b2b-lead-generation-claude-skills/ghosted-after-the-demo"><img src="https://agentmods.dev/badge/skills/mardab96/b2b-lead-generation-claude-skills/ghosted-after-the-demo/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/mardab96/b2b-lead-generation-claude-skills/ghosted-after-the-demo"><img src="https://agentmods.dev/badge/skills/mardab96/b2b-lead-generation-claude-skills/ghosted-after-the-demo.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.00057 | $0.01075 |
| Opus 5 | $0.00028 | $0.00537 |
| Sonnet 5 | $0.00011 | $0.00215 |
| Haiku 4.5 | $0.00006 | $0.00108 |
Grade A, and why
ghosted-after-the-demo 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 — 88 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ghosted After the Demo
Use this skill when
The call went well, everyone said the right things, and then nothing.
This is the most common and least examined failure in B2B selling. The default explanation is that they got busy, which is comfortable, occasionally true, and almost never the whole story. Silence after a good call usually means something was left unresolved in the call itself, and it was audible at the time.
Two versions of this skill's job: work out what actually happened, and write the message that has a chance of restarting it.
Required input
- The email thread, pasted, including your own messages.
- What was said on the call. Notes or transcript, whichever exists.
- How long the silence has run, and how many times you have followed up.
Helpful:
- who attended the call and who did not
- what the agreed next step was, and who owned it
- whether pricing was discussed and how it landed
- whether this pattern repeats across other deals
Analysis workflow
- Find the exact moment the tone changed. Read the thread in order and mark where enthusiasm turned into logistics, or where a question went unanswered.
- Check whether a real next step existed. "I will send something over" and "we will get back to you" are not next steps, and a deal with no owned next step goes quiet by default rather than by decision.
- Check who was in the room against who needs to approve. A great call with someone who cannot buy is the single most common cause of this silence, and it feels like progress right up until it stops.
- Look for the unasked question. Price, timing, incumbent contract, internal politics: whichever of these went unmentioned in a call where it obviously mattered is usually the reason.
- Count your own follow-ups and read their tone. Three messages that each say "just checking in" have taught them that ignoring you has no cost.
- Classify the silence honestly into one of: no authority, no budget cycle, no urgency, unspoken objection, lost to an incumbent, or genuinely busy. State the confidence.
- Write one message that fits the diagnosis, and decide whether this deal should be worked or closed.
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 · 88 lines · 57 tokens per session scan A 8bb593a484c7
ghosted-after-the-demo is a skill published in the GitHub repository mardab96/b2b-lead-generation-claude-skills (5 stars, last pushed 1mo ago), licensed MIT. It adds 57 tokens to every session and 1,075 once invoked, about $0.0003 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…