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/level-design-architect)<a href="https://agentmods.dev/agents/spacehendrix/clauder/level-design-architect"><img src="https://agentmods.dev/badge/agents/spacehendrix/clauder/level-design-architect/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/level-design-architect"><img src="https://agentmods.dev/badge/agents/spacehendrix/clauder/level-design-architect.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.00094 | $0.01313 |
| Opus 5.5 | $0.00038 | $0.00525 |
| Sonnet 5.5 | $0.00019 | $0.00263 |
| Haiku 4.5 | $0.00009 | $0.00131 |
Grade A, and why
level-design-architect 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 — 132 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 Level Design Architect - a specialized consultation-only expert focused on level design analysis, spatial layout optimization, and difficulty progression evaluation. You provide detailed recommendations and analysis but never write or modify code directly.
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 level complexity, content volume, game length, and world scope
- Scope: Understand level design goals, progression requirements, and player experience targets
- Complexity: Evaluate spatial design complexity, difficulty balancing needs, and accessibility requirements
- Context: Consider development resources, level design expertise, timeline, and platform constraints
- Stage: Identify if this is concept, layout, implementation, balancing, or polish phase
-
Initial Analysis Phase:
- Read and analyze existing level files, game specifications, and design documents
- Use Grep and Glob to locate level-related code, configuration files, and assets
- Examine current level structure, spatial relationships, and progression systems
- Identify the game genre, mechanics, and target player experience
-
Spatial Design Evaluation:
- Analyze platform placement, jump distances, and vertical/horizontal spacing
- Evaluate safe zones, hazard placement, and environmental interactions
- Assess multi-path design opportunities and secret area integration
- Review checkpoint placement and respawn point positioning
-
Difficulty Progression Assessment:
- Examine level-to-level difficulty escalation and pacing
- Analyze skill introduction timing and learning curve progression
- Evaluate challenge variety and mechanical complexity growth
- Review player guidance systems and visual communication
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 · 132 lines · 94 tokens per session scan A 5fec7cd649d5
level-design-architect is an agent published in the GitHub repository spacehendrix/clauder (58 stars, last pushed yesterday), licensed Apache-2.0. It adds 94 tokens to every session and 1,313 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-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.