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 won-deal-to-case-studygit 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/won-deal-to-case-study)<a href="https://agentmods.dev/skills/mardab96/b2b-lead-generation-claude-skills/won-deal-to-case-study"><img src="https://agentmods.dev/badge/skills/mardab96/b2b-lead-generation-claude-skills/won-deal-to-case-study/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/won-deal-to-case-study"><img src="https://agentmods.dev/badge/skills/mardab96/b2b-lead-generation-claude-skills/won-deal-to-case-study.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.00058 | $0.01087 |
| Opus 5 | $0.00029 | $0.00544 |
| Sonnet 5 | $0.00012 | $0.00217 |
| Haiku 4.5 | $0.00006 | $0.00109 |
Grade A, and why
won-deal-to-case-study 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.
Won Deal to Case Study
Use this skill when
The results exist and the proof does not.
Almost every B2B company has this problem in the same shape: several customers are demonstrably happy, everyone agrees a case study would help, and nobody writes one, because writing one from scratch takes a week and interviewing the customer takes a scheduling miracle.
Most of the material is already in the CRM. This assembles a draft from it, marks every gap the customer needs to fill, and writes the email that asks them.
Required input
- The deal: what they bought, when, and what the situation was before.
- Whatever exists in writing: CRM notes, call transcripts, the original proposal, onboarding messages, support threads.
Strongly improves the result:
- any number they have said out loud, even approximately
- what they tried before you
- the internal objection they had to overcome
- who the champion was and what their role is
Analysis workflow
- Reconstruct the before state from the record: what was actually happening when they started looking, in specifics. This is the part that makes a case study readable and the part most drafts skip.
- Find the trigger. Nobody buys because of a slow-burning inefficiency; they buy in the week something forced the issue. Locate that week.
- Separate what you can evidence from what you would like to claim. Every number goes in one of two buckets: stated by the customer, or not stated. There is no third bucket.
- Reconstruct what changed, in their operational terms rather than in product features.
- Mark every gap where the story needs the customer's own words, and be specific about which sentence you are asking them for.
- Draft the case study with the gaps visible as placeholders, so nobody accidentally publishes an inference as a quote.
- Decide what the story is actually about before writing a word of it. A case study about your product is a brochure; a case study about a company that had a problem and now does not is something a stranger reads to the end.
- Write the permission email. It is short, it says what you will publish, it offers approval before anything goes live, and it makes declining easy.
- Note who at your end owns chasing the approval, because this is the step where case studies die.
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 · 58 tokens per session scan A eb528901d6c4
won-deal-to-case-study is a skill published in the GitHub repository mardab96/b2b-lead-generation-claude-skills (5 stars, last pushed 1mo ago), licensed MIT. It adds 58 tokens to every session and 1,087 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…