case-studies-reference

case-studies-reference is a skill for Claude Code, Codex from Bbeierle12/Skill-MCP-Claude. It costs 57 tokens per session (641 once invoked), scanned A, original, MIT.

A reference guide to construction systems in games such as Fortnite, Rust, Valheim, Minecraft, No Man’s Sky, and Satisfactory. It compares mechanics including physics, scale, placement, stability, multiplayer, and upkeep.

In plain words
What is it for?
Use it when designing player-built structures, choosing grid or free placement, planning stability or decay, or evaluating multiplayer building systems.
Why use it?
It provides examples and tradeoffs from existing games when deciding how a building system should behave. It helps identify suitable patterns and common design mistakes.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it when designing player-built structures, choosing grid or free placement, planning stability or decay, or evaluating multiplayer building systems.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/bbeierle12/skill-mcp-claude/case-studies-reference
Install

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.

Any agent
npx skills add Bbeierle12/Skill-MCP-Claude --skill case-studies-reference
Clone the repo
git clone --depth 1 https://github.com/Bbeierle12/Skill-MCP-Claude

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for case-studies-reference

README.md
[![agentmods](https://agentmods.dev/badge/skills/bbeierle12/skill-mcp-claude/case-studies-reference.svg)](https://agentmods.dev/skills/bbeierle12/skill-mcp-claude/case-studies-reference)
Your own site
<a href="https://agentmods.dev/skills/bbeierle12/skill-mcp-claude/case-studies-reference"><img src="https://agentmods.dev/badge/skills/bbeierle12/skill-mcp-claude/case-studies-reference.svg" alt="Measured on agentmods" height="20"></a>
Per session 57 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 641 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00057 $0.00641
Opus 5 $0.00028 $0.00320
Sonnet 5 $0.00011 $0.00128
Haiku 4.5 $0.00006 $0.00064

Measured 8d ago against content hash c10b1671a6b4, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, from the pricing page.

Security

Grade A, and why

case-studies-reference 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 8d 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.

skills/case-studies-reference/SKILL.md · 46 lines

How it starts

The opening of the file, as written. The whole thing — 46 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Case Studies Reference

Detailed analysis of building systems from successful games, plus decision frameworks for new projects.

Quick Reference

Game Building Focus Physics Scale Key Innovation
Fortnite Combat/action Arcade Small Edit system, speed
Rust Survival/raids Heuristic Large Tool Cupboard, decay
Valheim Exploration Heuristic Medium Stability from ground
Minecraft Creativity None Infinite Voxel simplicity
No Man's Sky Base building Minimal Medium Snap points, free place
Satisfactory Factory Grid-based Large Hybrid grid/free

When to Use This Skill

Use case studies when making design decisions such as which physics model to implement, how to handle multiplayer building, choosing between grid and free placement, and deciding on decay/upkeep systems. The analyses provide concrete examples of trade-offs and their outcomes.

Reference Documents

See references/ for detailed documentation covering game-by-game breakdowns of building mechanics and performance strategies, decision matrices for common architectural choices, anti-patterns identified from games that struggled, and architectural recommendations organized by game genre.

Decision Framework

For quick decisions, use the matrices in game-analyses.md:

Physics Mode Selection: Are you building a survival game where building is about shelter? Use heuristic physics like Rust or Valheim. Is building core to moment-to-moment combat? Use arcade physics like Fortnite. Is engineering challenge the point? Consider realistic physics with caution since Medieval Engineers showed this approach frustrates most players.

Multiplayer Architecture: Competitive and PvP games require server-authoritative building with latency accepted as the cost of security. Cooperative games can use client prediction with server reconciliation for responsive feel. Single-player can use fully client-side for maximum responsiveness.

Read the full file on GitHub · 46 lines

Files

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.

Changes

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.

  1. 8d ago First seen · 46 lines · 57 tokens per session scan A c10b1671a6b4

Subscribe to this mod's changes

case-studies-reference is a skill published in the GitHub repository Bbeierle12/Skill-MCP-Claude (8 stars, last pushed today), licensed MIT. It adds 57 tokens to every session and 641 once invoked, about $0.0003 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-31.