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 SkillMedev/content-marketing-engine --skill case-study-buildergit clone --depth 1 https://github.com/SkillMedev/content-marketing-engineWrote 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/skillmedev/content-marketing-engine/case-study-builder)<a href="https://agentmods.dev/skills/skillmedev/content-marketing-engine/case-study-builder"><img src="https://agentmods.dev/badge/skills/skillmedev/content-marketing-engine/case-study-builder/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/skillmedev/content-marketing-engine/case-study-builder"><img src="https://agentmods.dev/badge/skills/skillmedev/content-marketing-engine/case-study-builder.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.00122 | $0.01629 |
| Opus 5.5 | $0.00049 | $0.00652 |
| Sonnet 5.5 | $0.00024 | $0.00326 |
| Haiku 4.5 | $0.00012 | $0.00163 |
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 17d 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.
This is a copy
100% identical to case-study-builder — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 116 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Case Study Builder
A case study sells by proof, not adjectives - the customer and the numbers do the talking. The costly mistake is writing it backwards: drafting marketing copy first and asking the customer to bless it, which produces approved-by-legal mush with no quotes worth reading and no numbers worth citing. Get the raw material first; the story is assembled, not invented.
Operating procedure
The order matters: interview before outline, numbers before draft. A draft written before the interview anchors on your product's talking points instead of the customer's actual story.
Step 1: Gather inputs
- The customer: company, industry, size, and the buyer persona this case study should persuade (default: mirror the customer's own profile - readers trust stories about companies like theirs).
- Access: can you interview the customer live (best), send written questions (acceptable), or only mine existing calls/emails/reviews (weakest - flag the limitation)?
- Any numbers already known: baseline metric, result metric, timeframe. Label estimates as estimates.
- Distribution target: web page, PDF leave-behind, or sales deck slide (default: one-page web layout).
Step 2: Run the interview - get the quote raw material first
Never draft before this step. Ask in this order, and record verbatim answers:
- "What was breaking, in your own words? What did it cost you - time, money, morale?" (problem + stakes)
- "What had you tried before? Why didn't it work?" (failed alternatives - this is where credibility lives)
- "What almost stopped you from buying?" (objection - the most persuasive quote in most case studies)
- "Walk me through what changed after. What can you do now that you couldn't?" (solution in their words)
- "What numbers moved? Even a rough range." (results - push politely: "was it closer to 10% or 50%?")
- "What would you tell someone in your seat considering this?" (the closing quote)
Keep quotes raw. "It was a dumpster fire every quarter-end" outsells "the process presented efficiency challenges." Clean grammar only; never sand off voice.
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.
- 17d ago Changed · +2 lines d5abd8e20ef4
- 1mo ago First seen · 114 lines · 122 tokens per session scan A 5734f7246f34
case-study-builder is a skill published in the GitHub repository SkillMedev/content-marketing-engine (1 stars, last pushed 17d ago), licensed MIT. It adds 122 tokens to every session and 1,629 once invoked, about $0.0005 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to case-study-builder, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
linkedin-post-writer
Write LinkedIn posts built for the feed - a hook that survives the two-line truncation, scannable one-idea-per-line structure, a comment-bait close, and first-hour engagement moves. Use when someone asks "write a LinkedIn post about this", "punch up my LinkedIn hook", "why did my post get no reach", or "turn this win…
tweet-thread-builder
Turn one idea into a tight tweet thread - a hook that earns the click, one beat per post, and momentum to a single CTA. Use when someone asks "turn this into a thread", "write a thread about my launch", "why did my thread flop", or "give me hook options for this". Do NOT use for LinkedIn-format posts - use…
social-caption-writer
Write one platform-native caption from a topic and brand voice, with a front-loaded hook, native length, and a single earned CTA. Use when the user gives a topic (and optionally brand voice or a described image/video) and asks for an Instagram, LinkedIn, X/Twitter, or TikTok caption. Do NOT use when the user wants a…
social-content-calendar
Builds a 4-week multi-platform posting calendar for a brand or social team, balancing content pillars, per-channel cadence, and real key dates into a week-by-week grid. Use when the user asks to plan, build, or audit a social content calendar or posting schedule across multiple channels (LinkedIn, X, Instagram…
social-hook-generator
Generates 10 labeled opening lines for a written social post, one per hook archetype, so the writer can test instead of guess. Use when drafting or rewriting the first line of a LinkedIn post, X post or thread, Instagram caption, or newsletter intro. Do NOT use when the hook is the spoken or on-screen opener of a…
hashtag-strategist
Builds a tiered hashtag and keyword set sized to the account's actual reach - mixing broad, niche, and branded tags per platform limits and screening out banned, spammy, or shadow-flagged tags. Use when someone asks "what hashtags should I use", "build me a hashtag set for this post", "audit my tag block", or is…