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 MRCalderon3D/everything-game-dev-code --skill game-feel-designgit clone --depth 1 https://github.com/MRCalderon3D/everything-game-dev-codeWrote 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/mrcalderon3d/everything-game-dev-code/game-feel-design)<a href="https://agentmods.dev/skills/mrcalderon3d/everything-game-dev-code/game-feel-design"><img src="https://agentmods.dev/badge/skills/mrcalderon3d/everything-game-dev-code/game-feel-design/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/mrcalderon3d/everything-game-dev-code/game-feel-design"><img src="https://agentmods.dev/badge/skills/mrcalderon3d/everything-game-dev-code/game-feel-design.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.00032 | $0.00466 |
| Opus 5.5 | $0.00013 | $0.00186 |
| Sonnet 5.5 | $0.00006 | $0.00093 |
| Haiku 4.5 | $0.00003 | $0.00047 |
Grade A, and why
game-feel-design 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.
What it actually says
Game Feel Design
Purpose
Design moment-to-moment feedback — hit-stop, screen shake, tweening, and response timing — so actions feel readable and satisfying.
Use When
- core actions feel flat, mushy, or unresponsive in playtests
- feedback layers (visual, audio, haptic) need a coherent budget and priority
- juice additions start hurting readability or competitive clarity
Inputs
- core loop and action set
- input-to-response timing measurements
- existing feedback inventory (VFX, SFX, camera, haptics)
- readability and accessibility constraints
Process
- inventory each player action and its current feedback stack
- define target response timing per action (anticipation, contact, recovery)
- assign feedback layers per action: animation, camera, audio, haptics, UI
- set a juice budget — where intensity helps and where it harms readability
- define tuning variables and exposure so feel can be iterated without code changes
- validate against accessibility needs (shake reduction, flash limits, haptic toggles)
Outputs
- feedback stack specification per core action
- response timing targets
- juice budget with readability limits
- tuning variable list for iteration
Quality Bar
- supports the core fantasy and player goals
- defines readable rules, edge cases, and feedback
- creates concrete hooks for tuning, telemetry, and QA
Common Failure Modes
- stacking effects until readability collapses
- tuning feel by anecdote without timing measurements
- feedback that cannot be reduced or disabled for accessibility
Related Agents
- gameplay-programmer
- ui-ux-designer
- audio-designer
Related Commands
- game-feel-pass
- audio-pass
- ui-flow-review
Related Skills
- accessibility-design
- combat-design
Notes
- Keep this skill aligned with the relevant rules layer and current project documentation.
- If engine-specific constraints materially change the workflow, hand off to the matching engine skill or engine-specific reviewer.
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 · 65 lines · 32 tokens per session scan A be375fc85ea9
game-feel-design is a skill published in the GitHub repository MRCalderon3D/everything-game-dev-code (98 stars, last pushed 17d ago), licensed MIT. It adds 32 tokens to every session and 466 once invoked, about $0.0001 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-09-03.
Other skills, from other repositories
cgs-design-system
Use for design system tasks that author a system GDD with rules, data, edge cases, progression, feedback, and implementation acceptance tests; produce verification evidence, changed or proposed files, and handoff boundaries.
cgs-prototype
Use for prototype tasks that build or plan a throwaway concept prototype around a falsifiable design hypothesis and cleanup boundary; produce verification evidence, changed or proposed files, and handoff boundaries.
cgs-release-checklist
Use for release checklist tasks that check build, packaging, store, QA, localization, accessibility, rollback, and ship/no-ship readiness; produce verification evidence, changed or proposed files, and handoff boundaries.
cgs-ui-ux-review
Use for ui ux review tasks that review UI and UX implementation for clarity, accessibility, localization, controller support, and player comprehension; produce verification evidence, changed or proposed files, and handoff boundaries.
cgs-standards-shader-code
Use for shader code standards: review target files, apply Codex-native boundaries, produce violations, fixes, verification evidence, and handoff notes.
cgs-standards-ui
Use for standards ui tasks that hUD, menus, accessibility, localization, controller navigation, and input states; produce verification evidence, changed or proposed files, and handoff boundaries.