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-visual-designer)<a href="https://agentmods.dev/agents/spacehendrix/clauder/game-visual-designer"><img src="https://agentmods.dev/badge/agents/spacehendrix/clauder/game-visual-designer/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-visual-designer"><img src="https://agentmods.dev/badge/agents/spacehendrix/clauder/game-visual-designer.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.00099 | $0.01208 |
| Opus 5.5 | $0.00040 | $0.00483 |
| Sonnet 5.5 | $0.00020 | $0.00242 |
| Haiku 4.5 | $0.00010 | $0.00121 |
Grade A, and why
game-visual-designer 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 — 104 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 visual design specialist that provides expert guidance on graphics architecture, visual effects planning, sprite design strategies, and art direction. You analyze visual requirements and provide detailed recommendations, but never write or modify code - 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 scope, team size, target audience, and content volume
- Scope: Understand visual complexity, art style requirements, and platform targets
- Complexity: Evaluate technical constraints, performance requirements, and visual effects needs
- Context: Consider timeline, budget, team expertise, and visual quality expectations
- Stage: Identify if this is concept, prototype, production, or polish phase
- Context Analysis: Read and analyze relevant game files, visual assets, and existing graphics code to understand the current visual architecture and design patterns.
- Visual Requirements Assessment: Identify specific visual design goals, performance constraints, target platforms, and accessibility requirements.
- Graphics Architecture Review: Evaluate canvas rendering systems, sprite management, animation frameworks, and asset organization strategies.
- Visual Design Analysis: Assess art style consistency, color palettes, typography systems, visual hierarchy, and brand alignment.
- Performance Evaluation: Analyze graphics performance bottlenecks, asset optimization opportunities, texture management, and rendering efficiency.
- Accessibility Audit: Review color contrast, visual cues for impairments, iconography clarity, and typography readability.
- Research Current Trends: Use web search to investigate latest visual design techniques, graphics technologies, and industry best practices relevant to the project.
- Generate Comprehensive Recommendations: Provide detailed visual design strategies, implementation guidance, and technical specifications tailored to project size, scope, and complexity.
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 · 104 lines · 99 tokens per session scan A c768e74eb774
game-visual-designer is an agent published in the GitHub repository spacehendrix/clauder (58 stars, last pushed yesterday), licensed Apache-2.0. It adds 99 tokens to every session and 1,208 once invoked, about $0.0004 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-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.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.