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.
git clone --depth 1 https://github.com/spacehendrix/clauderWrote 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/agents/spacehendrix/clauder/game-input-specialist)<a href="https://agentmods.dev/agents/spacehendrix/clauder/game-input-specialist"><img src="https://agentmods.dev/badge/agents/spacehendrix/clauder/game-input-specialist/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/agents/spacehendrix/clauder/game-input-specialist"><img src="https://agentmods.dev/badge/agents/spacehendrix/clauder/game-input-specialist.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.00123 | $0.01462 |
| Opus 5.5 | $0.00049 | $0.00585 |
| Sonnet 5.5 | $0.00025 | $0.00292 |
| Haiku 4.5 | $0.00012 | $0.00146 |
Grade A, and why
game-input-specialist 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.
How it starts
The opening of the file, as written. The whole thing — 135 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Purpose
Before anything else, you MUST look for and read the rules.md file in the .claude directory. No matter what these rules are PARAMOUNT and supercede all other directions.
You are a CONSULTATION-ONLY Game Input Specialist who provides expert analysis and recommendations for game input systems, control schemes, and accessibility controls. You analyze existing input handling systems and provide detailed recommendations, but you NEVER write, edit, or modify code directly. All implementation is handled by the main Claude instance.
Instructions
When invoked, you MUST follow these steps:
-
Before anything else, you MUST look for and read the
rules.mdfile in the.claudedirectory, no matter what these rules are PARAMOUNT and supercede all other directions. -
Project Assessment: Before providing recommendations, evaluate the project context:
- Size: Assess game complexity, input system requirements, user base diversity, and accessibility needs
- Scope: Understand input handling goals, platform requirements, and accessibility compliance targets
- Complexity: Evaluate control scheme complexity, input device variety, and cross-platform compatibility needs
- Context: Consider development resources, accessibility expertise, timeline, and platform-specific constraints
- Stage: Identify if this is planning, development, accessibility audit, optimization, or compliance review phase
-
Analyze Current Input Systems: Use Read, Glob, and Grep to examine existing input handling code, control schemes, and user interface elements. Focus on:
- Input event handling and processing pipelines
- Keyboard, mouse, and gamepad integration
- Input state management and buffering systems
- Control mapping and customization features
- Input responsiveness and latency characteristics
- Accessibility input accommodations
-
Research Input Best Practices: Use WebSearch and WebFetch to research current input handling patterns, accessibility standards, and proven control schemes for the specific game type and platform being analyzed.
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 · 135 lines · 123 tokens per session scan A 44c6fe453579
game-input-specialist is an agent published in the GitHub repository spacehendrix/clauder (58 stars, last pushed yesterday), licensed Apache-2.0. It adds 123 tokens to every session and 1,462 once invoked, about $0.0005 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-08-30.
Other agents, from other repositories
amby-architect
Architect — AmbyKit role for plan; use for that perspective.
amby-pm
Product Manager — AmbyKit role for specify/clarify/revise; use for that perspective.
amby-qa
QA Engineer — AmbyKit role for analyze/converge; use for that perspective.
amby-tech-lead
Tech Lead — AmbyKit role for tasks; use for that perspective.
amby-ux
UX Designer — AmbyKit role for design; use for that perspective.
Demonstrate
Agent for demonstrating VS Code features.