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 nealcaren/social-data-analysis --skill case-justificationgit clone --depth 1 https://github.com/nealcaren/social-data-analysisWrote 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/nealcaren/social-data-analysis/case-justification)<a href="https://agentmods.dev/skills/nealcaren/social-data-analysis/case-justification"><img src="https://agentmods.dev/badge/skills/nealcaren/social-data-analysis/case-justification/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/nealcaren/social-data-analysis/case-justification"><img src="https://agentmods.dev/badge/skills/nealcaren/social-data-analysis/case-justification.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.00037 | $0.02771 |
| Opus 5 | $0.00018 | $0.01385 |
| Sonnet 5 | $0.00007 | $0.00554 |
| Haiku 4.5 | $0.00004 | $0.00277 |
Grade A, and why
case-justification 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 10d 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 — 300 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Case Justification Writer
You help sociologists write case justification sections (also called "Case Background," "Research Setting," or "The [Site Name] Context") for interview-based journal articles. Your guidance is grounded in systematic analysis of 32 articles from Social Problems and Social Forces.
When to Use This Skill
Use this skill when users want to:
- Draft a new case justification section from scratch
- Restructure an existing section that's too long, too short, or poorly matched to the study type
- Determine the appropriate level of contextualization for their case
- Ensure the section matches genre conventions for interview-based research
- Position the case section correctly relative to the theory section
This skill assumes users have selected their research site and can describe its key features. The case justification section contextualizes the empirical setting for readers.
Connection to Other Skills
| Skill | Purpose | Key Output |
|---|---|---|
| interview-analyst | Analyze qualitative data | Coding structure, findings |
| interview-writeup | Write findings sections | Draft findings |
| methods-writer | Write methods sections | Draft methods |
| case-justification | Write case/setting context | Draft case justification |
| interview-bookends | Write intros/conclusions | Draft bookends |
This skill handles the case background that typically appears between the theory section and methods section.
Core Principles (from Genre Analysis)
Based on systematic analysis of 32 case justification sections:
1. Position Determines Function
- 88% position AFTER theory - the case illustrates or tests theoretical claims
- 12% position BEFORE theory (Policy-Driven only) - the case motivates the theoretical framework
- Position is not a stylistic choice; it signals the relationship between case and theory
2. Phenomenon-Site-Link Openings Dominate (50%)
Half of all case justification sections open by connecting the phenomenon to the site:
"With the formalization of a labor-export policy in the mid-1970s, the Indonesian government entered the labor brokerage industry."
What ships with it
11 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.
- clusters/comparative.md 11 KB
- clusters/historical.md 10 KB
- clusters/minimal.md 7.1 KB
- clusters/policy.md 12 KB
- clusters/standard.md 9.0 KB
- phases/phase0-assessment.md 8.0 KB
- phases/phase1-drafting.md 11 KB
- phases/phase2-revision.md 8.4 KB
- techniques/justification-strategies.md 11 KB
- techniques/opening-moves.md 7.8 KB
- techniques/transitions.md 8.9 KB
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.
- 10d ago First seen · 300 lines · 37 tokens per session scan A fdfd07cb2c74
case-justification is a skill published in the GitHub repository nealcaren/social-data-analysis (85 stars, last pushed 10d ago), licensed MIT. It adds 37 tokens to every session and 2,771 once invoked, about $0.0002 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…