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 ericrisco/rsc-harness --skill case-studiesgit clone --depth 1 https://github.com/ericrisco/rsc-harnessWrote 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/ericrisco/rsc-harness/case-studies)<a href="https://agentmods.dev/skills/ericrisco/rsc-harness/case-studies"><img src="https://agentmods.dev/badge/skills/ericrisco/rsc-harness/case-studies/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/ericrisco/rsc-harness/case-studies"><img src="https://agentmods.dev/badge/skills/ericrisco/rsc-harness/case-studies.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00078 | $0.02644 |
| Opus 5.5 | $0.00031 | $0.01058 |
| Sonnet 5.5 | $0.00016 | $0.00529 |
| Haiku 4.5 | $0.00008 | $0.00264 |
Grade A, and why
case-studies 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 1mo 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 — 143 lines — stays where its author put it; the contents beside it link to each section on GitHub.
case-studies
You write the consent-cleared, metrics-anchored story of a customer who already won — and the short attributed quote that travels with it. Your reader is the next skeptical buyer, not your own marketing team. Every line either advances that buyer's decision or it is cut.
A case study is a proof artifact, not a brochure. B2B buyers rank customer testimonials (55%) and case studies (54%) as top trust formats, just behind original research and peer insight (CMI/MarketingProfs, B2B Content Marketing: 2025 Benchmarks, Budgets & Trends, Oct 2024). They are reading to de-risk a purchase. A page that praises the vendor and hides the numbers fails that job no matter how polished the prose.
You produce two linked things: the case study (the full Challenge → Solution → Result story) and the portable testimonial quote (named, titled, one claim) that gets lifted onto a landing page, a slide, or a 30-second clip.
What this produces / route out first
If the request is not a single customer's measured outcome, hand it off before you write a word.
| The ask | Owner |
|---|---|
| Document one customer's measured win as proof for the next buyer | THIS skill |
| Sell the company vision/story to a room or investors | ../pitch-deck/SKILL.md |
| Long-form / SEO thought-leadership with no single named customer | ../article-writing/SKILL.md |
| Keep an existing customer happy — QBR, expansion, churn-save | ../retention/SKILL.md |
| Solicit or reply to public reviews / ratings | ../review-management/SKILL.md |
| The reusable cross-channel tone-of-voice rules | ../brand-voice/SKILL.md |
| Drop the proven quote into a converting page | ../landing-copy/SKILL.md |
| Price the offer this win justifies | pricing |
The one-sentence call: it is a case study if a real, named customer already got a measured result and consented to be quoted.
The intake gate — STOP if any of these is missing
Do not start prose until you have all three. A missing piece is a gathering task or an anonymization decision, never an invention.
What ships with it
5 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.
- 1mo ago First seen · 143 lines · 78 tokens per session scan A 9c57447a77a3
case-studies is a skill published in the GitHub repository ericrisco/rsc-harness (340 stars, last pushed today), licensed MIT. It adds 78 tokens to every session and 2,644 once invoked, about $0.0003 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-30.
Other skills, from other repositories
merge-aliases
Folds two surface names for the same backend system into one canonical entity, keeping every original mention individually retrievable, and refuses to merge pairs that only share spelling.
anchor-and-lock
Consults a check that sits outside the loop system before finalizing any decision the frozen facts bear on, and refuses every attempt by a loop to rewrite a node marked frozen, regardless of how convergent the loop's own reasoning looks.
counter-metric-check
Compares a watched loop's headline reading against an independently owned counter-metric reading for each period in a governance graph, and produces a governance edge for every period where the counter-metric crosses its recorded ceiling.
traverse-multi-hop
Expresses a multi-hop lineage question as a single variable-length path match against native graph storage, bounded by an explicit hop depth and an explicit relationship-type allowlist, instead of a recursive relational join that grows one level per hop.
attach-receipts
Attaches sourcedoc/extractionrunid/schemaversion receipts to every edge at write time, and refuses to write any edge missing one of the three.
query-graph
Loads schema.sql into a local SQLite file, then answers availability and provenance questions against the nodes/edges tables with real SQL instead of re-reading source material.