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 charlieviettq/awesome-agent-skill --skill grad-case-studygit clone --depth 1 https://github.com/charlieviettq/awesome-agent-skillWrote 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/charlieviettq/awesome-agent-skill/grad-case-study)<a href="https://agentmods.dev/skills/charlieviettq/awesome-agent-skill/grad-case-study"><img src="https://agentmods.dev/badge/skills/charlieviettq/awesome-agent-skill/grad-case-study/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/charlieviettq/awesome-agent-skill/grad-case-study"><img src="https://agentmods.dev/badge/skills/charlieviettq/awesome-agent-skill/grad-case-study.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.00097 | $0.01128 |
| Opus 5 | $0.00048 | $0.00564 |
| Sonnet 5 | $0.00019 | $0.00226 |
| Haiku 4.5 | $0.00010 | $0.00113 |
Grade A, and why
"grad-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 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.
This is a copy
95% identical to grad-case-study — 8 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 120 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Case Study Research (Yin)
Overview
Case study research is an empirical inquiry that investigates a contemporary phenomenon in depth and within its real-life context, especially when the boundaries between phenomenon and context are not clearly evident. Yin's framework provides systematic design choices — single vs. multiple cases, holistic vs. embedded analysis — and emphasizes triangulation to strengthen construct validity.
When to Use
- Research questions are "how" or "why" questions about contemporary events
- The researcher has little or no control over behavioral events
- Contextual conditions are highly pertinent to the phenomenon of study
- Boundaries between phenomenon and context are blurred
When NOT to Use
- When frequency or incidence data is needed (use survey or experiment)
- When context is irrelevant and can be controlled (use experiment)
- When the goal is statistical generalization to a population
Assumptions
IRON LAW: Case study answers HOW and WHY questions in context — if you
need frequency or incidence data, use a survey or experiment instead.
Applying case study to "how many" or "how much" questions misuses the
methodology.
Key assumptions:
- The case is a bounded system — define temporal, spatial, and conceptual boundaries
- Multiple sources of evidence are essential for construct validity
- Multiple cases follow replication logic (not sampling logic) — each case is an experiment, not a survey respondent
- A case study protocol and database enhance reliability
Methodology
Step 1: Design the Case Study
Define the research question (how/why). Select the case type using Yin's 2x2 matrix:
| Single Case | Multiple Case | |
|---|---|---|
| Holistic (single unit) | Critical, unique, or revelatory case | Literal or theoretical replication |
| Embedded (multiple units) | Multiple units within one case | Multiple units across cases |
Develop propositions to guide data collection.
Step 2: Collect Evidence from Multiple Sources
What ships with it
1 file 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 · 120 lines · 97 tokens per session scan A ae599a75fc13
"grad-case-study" is a skill published in the GitHub repository charlieviettq/awesome-agent-skill (26 stars, last pushed 1mo ago), licensed MIT. It adds 97 tokens to every session and 1,128 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it A with 0 findings. It is 95% identical to grad-case-study, differing in 8 lines, and is treated as a copy.
Other skills, from other repositories
learn-from-fix
Capture Elixir/Ecto/LiveView lessons and Hex API rules. Use after corrections or when asked to document learning, record a lesson, prevent a fixed mistake, or remember package guidance with --library.
elixir-idioms
OTP/BEAM patterns and Elixir idioms — GenServer, Supervisor, Task, Registry, pattern matching, with chains, pipes. Use when designing processes or debugging BEAM issues.
examples
Provide Phoenix, LiveView, Ecto, OTP, or Oban examples. Use when asked for sample code, a walkthrough, a proper implementation, or expected workflow output. Pair with domain skills. NOT for debugging, direct changes, best-practice advice, or audits.
intro
Walk through the Elixir/Phoenix plugin commands, workflow, and features in 6 interactive sections. Use when a new user wants to learn what the plugin offers or needs a refresher on available commands.
toolbox-talk-generator
Generate safety toolbox talks for construction crews. Create contextual safety briefings based on weather, work activities, and recent incidents. Support multiple languages.
knowledge-map
Guide-and-script skill for building course knowledge maps. Use it to turn a course topic, syllabus, textbook outline, notes, or teaching materials into a structured framework, key concept explanations, concept dependencies, and optional Markdown / Markmap / Mermaid / OPML / HTML outputs.