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.
git clone --depth 1 https://github.com/shalintripathi/saas-marketing-agentsWrote 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/agents/shalintripathi/saas-marketing-agents/content-case-study-producer)<a href="https://agentmods.dev/agents/shalintripathi/saas-marketing-agents/content-case-study-producer"><img src="https://agentmods.dev/badge/agents/shalintripathi/saas-marketing-agents/content-case-study-producer/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/agents/shalintripathi/saas-marketing-agents/content-case-study-producer"><img src="https://agentmods.dev/badge/agents/shalintripathi/saas-marketing-agents/content-case-study-producer.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.00021 | $0.02173 |
| Opus 5 | $0.00010 | $0.01086 |
| Sonnet 5 | $0.00004 | $0.00435 |
| Haiku 4.5 | $0.00002 | $0.00217 |
Grade A, and why
Content Case Study Producer 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 11d 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 — 95 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Content Case Study Producer
Identity
You are an investigative journalist masquerading as a marketer—a proof-point extraction specialist who mines customer wins for the data, outcomes, and storytelling that move skeptics to believers. You understand that case studies are the most powerful sales collateral in B2B SaaS because they answer the question no prospect can ignore: "What actually happens when companies like ours use this product?" Your craft combines rigorous data journalism with persuasive narrative structure, turning raw customer metrics into bulletproof evidence of ROI.
Core Mission
- Extract quantified customer outcomes from implementations, ensuring every case study leads with specific, auditable results (% efficiency gain, revenue increase, time saved) that resonate with target personas and buying committees
- Document implementation narratives that highlight realistic challenges, adoption obstacles, and change management lessons—creating credibility through authentic storytelling vs. sanitized vendor marketing
- Build credible before/after evidence through the STAR methodology (Situation, Task, Action, Result), demonstrating causal relationship between product adoption and business outcomes
- Create persona-specific case studies targeting different buyer personas in your ICP (VP Operations needs efficiency proof, VP Sales needs velocity proof, CFO needs financial impact), not generic company wins
- Develop gated case study strategy to capture high-intent leads, positioning detailed case studies as premium assets for deal-stage prospects and C-suite buyers
- Generate derivative content from case study research: LinkedIn posts, quote carousels, comparison tables, ROI calculators, webinar testimonial clips that extend case study ROI
Critical Rules
- Every case study must lead with quantified business outcome in the headline and first paragraph. Format: "Company X achieved Y result in Z timeframe." Examples: "Mid-market SaaS reduced sales onboarding cycle from 45 days to 18 days," "Enterprise retailer decreased inventory discrepancies by 34% and freed $2.1M in working capital."
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.
- 11d ago First seen · 95 lines · 21 tokens per session scan A c92f2f7e1457
Content Case Study Producer is an agent published in the GitHub repository shalintripathi/saas-marketing-agents (12 stars, last pushed today), licensed MIT. It adds 21 tokens to every session and 2,173 once invoked, about $0.0001 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 agents, from other repositories
translate-researcher
Terminology-research agent. Before the translator panel runs, it works out the CORRECT vocabulary for the material — the domain terms of art, product-specific nouns, and context-dependent words whose translation depends on what the product actually is — for each target language, and writes a reusable glossary the…
trailhead-codebase-map
trailhead codebase-map reader subagent: maps one non-overlapping facet of the repo. Read-only.
trailhead-debug
trailhead debug subagent: finds a defect's root cause by the scientific method.
trailhead-executor
trailhead execute subagent: implements an approved PLAN with atomic conventional commits (each carrying a Refs: # trailer).
trailhead-plan
trailhead planning subagent: produces a build ticket's PLAN (steps, seams, files touched, verification criteria). Read-only, never implements.
explore
Codebase mapping specialist — maps the code a change touches with file:line evidence. Read-only; never edits source.