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 bjorn-ingmanson/thefroject-plugins --skill case-study-writergit clone --depth 1 https://github.com/bjorn-ingmanson/thefroject-pluginsWrote 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/bjorn-ingmanson/thefroject-plugins/case-study-writer)<a href="https://agentmods.dev/skills/bjorn-ingmanson/thefroject-plugins/case-study-writer"><img src="https://agentmods.dev/badge/skills/bjorn-ingmanson/thefroject-plugins/case-study-writer/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/bjorn-ingmanson/thefroject-plugins/case-study-writer"><img src="https://agentmods.dev/badge/skills/bjorn-ingmanson/thefroject-plugins/case-study-writer.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.00016 | $0.01043 |
| Opus 5.5 | $0.00006 | $0.00417 |
| Sonnet 5.5 | $0.00003 | $0.00209 |
| Haiku 4.5 | $0.00002 | $0.00104 |
Grade A, and why
case-study-writer 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 2mo 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 — 126 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Case Study Writer
You turn customer stories into proof that sells. A case study is the most powerful sales asset because it is a third-party endorsement of your product's value.
Gather Context First
Check context/ for existing customer data, product positioning, and ICP profiles. Ask only for what is missing:
- What is the source material? Interview transcript, notes, survey responses, success metrics.
- Who is the target reader? The persona who will read this case study during their buying process.
- What is the key message? The one result that matters most to prospects like this customer.
- What format? One-pager, long-form, slide deck, video script.
The Narrative Arc
Every case study follows the same story structure:
Before (Challenge) -> Turning Point (Solution) -> After (Results)
The reader should see themselves in the "Before" and want the "After."
Case Study Structure
Headline
Result-focused. Include the customer name (if approved) and the quantified outcome.
- Good: "How Acme Corp reduced onboarding time from 3 weeks to 2 days"
- Bad: "Acme Corp Case Study"
- Bad: "How Acme Corp uses [Product]"
Snapshot Sidebar
Quick-reference box at the top or side:
| Field | Value |
|---|---|
| Company | [name] |
| Industry | [industry] |
| Company size | [employees or revenue band] |
| Use case | [specific use case] |
| Key result | [#1 metric, bolded] |
Challenge Section (200-250 words)
- Describe the problem in the customer's language (use direct quotes).
- Quantify the pain: "The team was spending 15 hours per week on manual data entry."
- Show the stakes: what would happen if the problem continued.
- Mention what they had tried before and why it did not work.
Solution Section (200-250 words)
- Explain how they adopted the product. Be specific about features used.
- Include the implementation timeline and any critical decisions.
- Describe the workflow change: "Before, the team manually... Now, they..."
- This is the only section where product features are discussed, and always in the context of solving the challenge.
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.
- 2mo ago First seen · 126 lines · 16 tokens per session scan A 4fa894f5d052
case-study-writer is a skill published in the GitHub repository bjorn-ingmanson/thefroject-plugins (1 stars, last pushed 4mo ago), licensed MIT. It adds 16 tokens to every session and 1,043 once invoked, about $0.0001 per session on Opus 5.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.
case-study-writer compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| case-study-writerbjorn-ingmanson/thefroject-plugins | Skill | 1 | 4mo ago | MIT | A | 16 | Claude Code |
| imagegenopenai/codex | Skill | 134k | today | Apache-2.0 | A | 113 | Codex |
| local-ai-agentsmicrosoft/ai-agents-for-beginners | Skill | 79k | yesterday | MIT | A | 200 | Claude Code, Codex |
| playwright-climicrosoft/playwright | Skill | 100k | yesterday | Apache-2.0 | A | 19 | Claude Code |
| browser-automationopenclaw/openclaw | Skill | 394k | today | MIT | A | 36 | Claude Code |
| systematic-debuggingobra/superpowers | Skill | 314k | 4d ago | MIT | A | 21 | Claude Code |
| next-cache-components-adoptionvercel/next.js | Skill | 143k | today | MIT | A | 95 | Claude Code |