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 agentmods add skills/realjaymes/marketingagentskills/case-study-buildernpx skills add realjaymes/marketingagentskills --skill case-study-buildergit clone --depth 1 https://github.com/realjaymes/marketingagentskillsWrote 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/realjaymes/marketingagentskills/case-study-builder)<a href="https://agentmods.dev/skills/realjaymes/marketingagentskills/case-study-builder"><img src="https://agentmods.dev/badge/skills/realjaymes/marketingagentskills/case-study-builder.svg" alt="Measured on agentmods" 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 | $0.00047 | $0.00837 |
| Opus 5 | $0.00023 | $0.00418 |
| Sonnet 5 | $0.00009 | $0.00167 |
| Haiku 4.5 | $0.00005 | $0.00084 |
Grade A, and why
case-study-builder 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 5d 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 — 130 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Case Study Builder Assistant
Generate structured case studies, engagement summaries, and project documentation using structured frameworks.
When to Use
- User wants to create a case study or success story
- User needs to document a client engagement
- User mentions: case study, client story, engagement summary, project summary, portfolio, results documentation
Output Types
- Company Summary: Quick company context
- Engagement Summary: Challenge, Solution, Results, Testimonial format
- Project Summary: Objective, Execution, Outcomes format
- Full Case Study: Comprehensive client story
Instructions
- Identify output type needed
- Collect inputs based on framework
- Generate structured output following templates
- Include quantitative results where available
Company Summary Framework
Format 1: Full Context
[Company name], [funding stage], [industry], [product category], [region], [website]
Example: Reform, Bootstrapped, MarTech, Lead Gen Form Builder SaaS, USA, www.reform.app
Format 2: Short
[Company Name] ([Business Model], [Product/Service Category])
Example: FunnelEnvy (B2B, Growth Marketing Service Provider)
Company Intro Template
[Company Name] is [Product/Service Category] for [persona + company type + industry + region] to [use case]
Engagement Summary Framework
## [Company Name] - Engagement Summary
**Challenge:**
[Brief summary of the primary problem the company faced]
**Solution:**
[Brief summary of the solutions implemented]
**Results:**
[One-liner about key improvements achieved]
**Testimonial:**
"[Customer quote]" - [Name], [Title], [Company]
Inputs Needed
- Company name and context
- Primary challenge/problem
- Solutions implemented
- Measurable results
- Client quote (or draft one)
Project Summary Framework
## [Project Title]
**Objective:**
[1-2 lines, 15-30 words: short statement of goal]
**Execution:**
- [Tool/method/framework 1]
- [Tool/method/framework 2]
- [Tool/method/framework 3]
**Outcomes:**
- [Quantitative/qualitative impact 1]
- [Quantitative/qualitative impact 2]
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 5d ago First seen · 130 lines · 47 tokens per session scan A 8c6b83eed69d
case-study-builder is a skill published in the GitHub repository realjaymes/marketingagentskills (56 stars, last pushed 8d ago), licensed MIT. It adds 47 tokens to every session and 837 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-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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…