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 commands/brainbytes-dev/everything-claude-marketing/case-studygit clone --depth 1 https://github.com/brainbytes-dev/everything-claude-marketingWhat 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.00020 | $0.02164 |
| Opus 5 | $0.00010 | $0.01082 |
| Sonnet 5 | $0.00004 | $0.00433 |
| Haiku 4.5 | $0.00002 | $0.00216 |
Grade A, and why
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 2d 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 — 231 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/case-study
Write a compelling customer case study in the challenge-solution-results format with a strong narrative arc, quotable metrics, and persuasive storytelling.
What This Command Does
This command creates a complete customer case study that transforms a customer success story into a persuasive marketing asset. It follows the proven challenge-solution-results structure while weaving in narrative elements that make the story relatable and memorable. The output includes a compelling headline, customer snapshot, the full case study narrative, pull quotes, a metrics sidebar, and recommendations for how to distribute and repurpose the story. The case study is designed to work across formats — as a standalone PDF, website page, sales enablement asset, and source material for social content.
When to Use
- Documenting a customer success story for your website or resource library
- Creating sales enablement content that proves ROI
- Building credibility for a specific use case, industry, or company size
- Supporting a product launch with real-world validation
- Strengthening a proposal with relevant proof points
- Generating content for social media, email, and conference presentations
- Building a library of proof points organized by industry, use case, or outcome
How It Works
- Gathers the story — Asks about the customer, their challenge, your solution, and the measurable results
- Identifies the narrative angle — Finds the most compelling thread that ties the story together
- Structures the case study — Builds the challenge-solution-results framework with clear sections
- Writes the narrative — Creates engaging prose that balances storytelling with specificity
- Crafts quotes — Writes natural-sounding customer quotes that capture key moments and outcomes
- Highlights metrics — Surfaces the most impressive numbers and presents them for maximum impact
- Creates the summary — Builds a quick-scan version with headline stats for busy readers
- Plans distribution — Recommends how to use the case study across channels and formats
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.
- 2d ago First seen · 231 lines · 20 tokens per session scan A 5aa66a65d498
case-study is a command published in the GitHub repository brainbytes-dev/everything-claude-marketing (5 stars, last pushed 5mo ago), licensed MIT. It adds 20 tokens to every session and 2,164 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 commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
constitution
Create or update the project constitution from interactive or provided principle inputs.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.