Borrowing it
Nothing to install: this file belongs to mtarcure/claude-vibe-squad. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/mtarcure/claude-vibe-squad/main/.agents/skills/level-design-patterns/SKILL.mdgit clone --depth 1 https://github.com/mtarcure/claude-vibe-squadWrote 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/mtarcure/claude-vibe-squad/level-design-patterns)<a href="https://agentmods.dev/skills/mtarcure/claude-vibe-squad/level-design-patterns"><img src="https://agentmods.dev/badge/skills/mtarcure/claude-vibe-squad/level-design-patterns.svg" alt="Measured on agentmods" 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.00066 | $0.00260 |
| Opus 5 | $0.00033 | $0.00130 |
| Sonnet 5 | $0.00013 | $0.00052 |
| Haiku 4.5 | $0.00007 | $0.00026 |
Grade A, and why
level-design-patterns 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.
What it actually says
Level Design Patterns
Turn a game-design contract into playable level structure: layout, pacing, gating, and a difficulty curve.
Steps
- Read the upstream game-design contract; derive the experience pillars the levels must serve.
- Block out spaces and critical paths; place gates and rewards to control pacing.
- Map the difficulty curve against explicit player-skill assumptions (teach → test → twist).
- Annotate each beat with the intended feeling and the mechanic that produces it.
- Mark playtest assertions per level (completable, no soft-locks, curve holds).
- Return any unimplementable runtime trigger to
game-engineeras an unresolved requirement.
Acceptance
- Every referenced mechanic exists in the upstream game-design contract.
- The difficulty curve is intentional and tied to stated skill assumptions.
- Each level carries playtest assertions and has no dangling triggers.
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.
- 8d ago First seen · 23 lines · 66 tokens per session scan A 302166943023
level-design-patterns is a skill published in the GitHub repository mtarcure/claude-vibe-squad (109 stars, last pushed 3d ago), licensed MIT. It adds 66 tokens to every session and 260 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-30.
Other skills, from other repositories
contributor-onboarding
Help a new contributor get productive on this checkout - inspect sync state against main, build, run the repository's exact verification gate, and produce a local what's-new digest. Never fetches, pulls, or modifies a dirty tree on its own. Explicit-only.
codew-release-qa-sweep
Use before claiming Codewhale release work is done: run the full gate sweep and list the manual QA targets.
gh-file-issue
Use when filing a new Codewhale GitHub issue: turn a bug or idea into a well-formed, actionable issue with repro, acceptance criteria, labels, and milestone.
gh-find-prs
Survey open Codewhale PRs and triage each for mergeability and disposition against the real landing branch.
gh-treasure-hunt
Hunt the issue/PR queue for highest value-over-risk wins: clean focused community PRs, already-implemented issues to close, safe quick-fixes.
recording
Capture screen recordings and screenshots on any registered computer (macOS, Windows, Linux, HarmonyOS) and manage the recording library.