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 kyu-n/gdx-claude-skills --skill libgdx-input-handlinggit clone --depth 1 https://github.com/kyu-n/gdx-claude-skillsWrote 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/kyu-n/gdx-claude-skills/libgdx-input-handling)<a href="https://agentmods.dev/skills/kyu-n/gdx-claude-skills/libgdx-input-handling"><img src="https://agentmods.dev/badge/skills/kyu-n/gdx-claude-skills/libgdx-input-handling/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/kyu-n/gdx-claude-skills/libgdx-input-handling"><img src="https://agentmods.dev/badge/skills/kyu-n/gdx-claude-skills/libgdx-input-handling.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.00070 | $0.03417 |
| Opus 5 | $0.00035 | $0.01708 |
| Sonnet 5 | $0.00014 | $0.00683 |
| Haiku 4.5 | $0.00007 | $0.00342 |
Grade A, and why
libgdx-input-handling 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 11d 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 — 292 lines — stays where its author put it; the contents beside it link to each section on GitHub.
libGDX Input Handling
Reference for polling vs event-driven input, InputProcessor, InputMultiplexer, GestureDetector, coordinate unprojection, and platform input quirks.
Polling vs Event-Driven
Polling — check input state each frame in render():
// isKeyPressed = true EVERY frame while held → continuous actions (movement)
if (Gdx.input.isKeyPressed(Input.Keys.W)) player.y += speed * delta;
if (Gdx.input.isKeyPressed(Input.Keys.SPACE)) fireBullet();
// isKeyJustPressed = true ONLY on the first frame the key goes down → one-shot actions
if (Gdx.input.isKeyJustPressed(Input.Keys.ESCAPE)) togglePause();
if (Gdx.input.isKeyJustPressed(Input.Keys.SPACE)) jump(); // fires once per press
// Touch/mouse
if (Gdx.input.isTouched()) {
int screenX = Gdx.input.getX(); // screen coords, Y-down
int screenY = Gdx.input.getY();
}
if (Gdx.input.isTouched(1)) { /* second finger */ }
if (Gdx.input.justTouched()) { /* first frame of touch only */ }
isKeyPressed vs isKeyJustPressed: Using isKeyJustPressed for movement causes stuttering (only moves one frame per key press). Using isKeyPressed for a one-shot action like jumping causes repeated firing every frame the key is held.
Event-driven — implement InputProcessor and register it:
Gdx.input.setInputProcessor(myProcessor);
Use polling for continuous actions (movement, held buttons). Use event-driven for discrete actions (clicks, key presses, gestures).
InputProcessor Interface
All 9 methods — every one returns boolean:
public interface InputProcessor {
boolean keyDown(int keycode); // physical key pressed
boolean keyUp(int keycode); // physical key released
boolean keyTyped(char character); // Unicode character generated
boolean touchDown(int screenX, int screenY, int pointer, int button); // finger/mouse down
boolean touchUp(int screenX, int screenY, int pointer, int button); // finger/mouse up
boolean touchCancelled(int screenX, int screenY, int pointer, int button); // touch cancelled by OS
boolean touchDragged(int screenX, int screenY, int pointer); // move while touching
boolean mouseMoved(int screenX, int screenY); // mouse move (desktop only)
boolean scrolled(float amountX, float amountY); // scroll wheel / touchpad
}
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.
- 11d ago First seen · 292 lines · 70 tokens per session scan A d4b7e51bd25d
libgdx-input-handling is a skill published in the GitHub repository kyu-n/gdx-claude-skills (4 stars, last pushed 7mo ago), licensed MIT. It adds 70 tokens to every session and 3,417 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.
Other skills, from other repositories
cesiumjs-models-particles
CesiumJS models, glTF, and particle effects - Model, KHRmeshoptcompression, CAD glTF extensions, EdgeDisplayMode, ModelAnimation, ModelNode, ParticleSystem, emitters, GPM extensions. Use when loading compressed or CAD-style glTF/GLB models, controlling edge rendering, playing model animations, positioning particles…
cesiumjs-materials-shaders
CesiumJS materials and post-processing — Material, Fabric JSON, MaterialAppearance, ImageBasedLighting, PostProcessStage, PostProcessStageLibrary, bloom, depth of field, ambient occlusion, FXAA, tonemapping, BlendingState. Use when defining Fabric materials for entities or primitives, configuring PBR image-based…
atmosphere-shader
Generate physically-based atmospheric scattering shaders — sky domes, planetary atmospheres, LUT-optimized pipelines, depth-aware post-processing. Four modes — sky-dome, atmosphere-post, planet, lut. Triggers on atmospheric scattering, sky shader, sunset rendering, planet atmosphere, Rayleigh scattering, Mie…
particle-swarm-sim
Generate 20,000+ particle swarm simulators in two modes: sandbox (complete Three.js host runtime with gesture controls, security validation, code injection pipeline) and sim (behavior function bodies that position/color particles via a sandboxed API). The AI writes ONLY a function body — the host handles rendering…
sprite-forge
Generate game sprites, SVG characters, ASCII art, animated mascots, and isometric turnarounds from images or descriptions. Five output modes: SVG characters, game sprite sheets with atlas metadata, 8-way isometric turnarounds, ASCII/Unicode terminal art, GSAP-animated mascots. Triggers on sprite, pixel art, SVG…
meshy-3d-generation
Generate 3D models, textures, images, rig characters, and animate them using the Meshy AI API. Handles API key detection, setup, and all generation workflows via direct HTTP calls. Use when the user asks to create 3D models, convert text/images to 3D, texture models, rig or animate characters, or interact with the…