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 nthnclrk/enablement-skills --skill case-study-extractorgit clone --depth 1 https://github.com/nthnclrk/enablement-skillsWrote 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/nthnclrk/enablement-skills/case-study-extractor)<a href="https://agentmods.dev/skills/nthnclrk/enablement-skills/case-study-extractor"><img src="https://agentmods.dev/badge/skills/nthnclrk/enablement-skills/case-study-extractor/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/nthnclrk/enablement-skills/case-study-extractor"><img src="https://agentmods.dev/badge/skills/nthnclrk/enablement-skills/case-study-extractor.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.00082 | $0.00678 |
| Opus 5 | $0.00041 | $0.00339 |
| Sonnet 5 | $0.00016 | $0.00136 |
| Haiku 4.5 | $0.00008 | $0.00068 |
Grade A, and why
case-study-extractor 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 9d 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 — 65 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Case study extractor
Permissioned proof. Evidence strength and permission to publish are different decisions.
If the metric has no baseline, it is not a result yet. If the quote is reconstructed from a summary, it is not a quote.
Honest. "In a three-customer pilot, unresolved handoffs fell 28% in 60 days. Directional. Not a benchmark. Named use requires customer approval we do not have."
Overclaim. "Customers cut delivery delays by 28% with MosaicOps."
Default to internal. Mark every external-use field Not approved or Unknown until you have the permission.
Confirm Inputs First
Ask only for what changes claim strength or reuse:
- Intended output and audience
- Source packet with locators
- Metric definition, baseline, period, population
- Permission for name, logo, each quote, each metric, channel, and expiry
Do not invent numbers, quotes, or approvals.
Read The Right Reference
Read references/case-study-template.md for claim statuses, the permission matrix, and story shape. Skip it if you are only extracting a quote bank.
Default Workflow
- Set the boundary. Sources, audience, and reuse permissions before any narrative. Strength and permission stay separate.
- Extract units. Starting state, problem, intervention, adoption, result. Source IDs on each. Keep conflicts.
- Validate numbers. Definition, baseline, result, period, population, calculation, attribution limit. Opinion is not causality.
- Handle quotes exactly. Verbatim, with speaker, date, context, locator. Paraphrases stay outside quotation marks.
- Classify claims:
Verified,Supported,Anecdotal,Unverified. Publication status is a different field. - Tell the story only where the evidence links challenge, approach, and outcome. Keep the conditions that limit transfer.
- Produce the smallest requested branch: quote bank, proof-point packet, internal narrative, customer-review draft, or publication packet.
What ships with it
2 files 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.
- 9d ago First seen · 65 lines · 82 tokens per session scan A e16ebb5ff4dc
case-study-extractor is a skill published in the GitHub repository nthnclrk/enablement-skills (13 stars, last pushed 19d ago), licensed MIT. It adds 82 tokens to every session and 678 once invoked, about $0.0004 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.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…