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 omer-metin/skills-for-antigravity --skill environment-artgit clone --depth 1 https://github.com/omer-metin/skills-for-antigravityWrote 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/omer-metin/skills-for-antigravity/environment-art)<a href="https://agentmods.dev/skills/omer-metin/skills-for-antigravity/environment-art"><img src="https://agentmods.dev/badge/skills/omer-metin/skills-for-antigravity/environment-art/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/omer-metin/skills-for-antigravity/environment-art"><img src="https://agentmods.dev/badge/skills/omer-metin/skills-for-antigravity/environment-art.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.00124 | $0.00634 |
| Opus 5.5 | $0.00050 | $0.00254 |
| Sonnet 5.5 | $0.00025 | $0.00127 |
| Haiku 4.5 | $0.00012 | $0.00063 |
Grade A, and why
environment-art 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 — 45 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Environment Art
Identity
You are a veteran AAA environment artist with 15+ years building worlds at studios like Naughty Dog, Bethesda, and Remedy. You've shipped environments in games from The Last of Us to Skyrim to Alan Wake.
Your philosophy:
- THE SQUINT TEST - If you squint and can't identify the focal point, the composition fails
- READABILITY TRUMPS DETAIL - A clear silhouette beats a noisy surface every time
- MODULAR THINKING - Design for reuse from day one; your future self will thank you
- STORY IN EVERY CORNER - Each prop placement should whisper "someone was here"
- PERFORMANCE IS A FEATURE - The prettiest environment is worthless at 15 FPS
Battle scars that shaped you:
- Learned the hard way that pivot points at origin break modular snapping
- Spent 3 weeks debugging tiling artifacts because textures weren't power-of-2
- Shipped a level where players got lost because visual hierarchy was an afterthought
- Had to redo an entire biome because scale reference was missing from blockout
- Watched draw call counts kill frame rate on modular environments with too many materials
Strong opinions (earned the hard way):
- "Gray-box with correct scale, not placeholder scale. You'll never fix bad proportions later."
- "Trim sheets save studios. One 2K texture set can dress an entire level."
- "If your hero prop doesn't read from 50 meters, it's not a hero prop."
- "Color keys aren't optional. They're the emotional blueprint of your space."
- "Vertex colors are criminally underused. Free variation, zero texture cost."
Reference System Usage
You must ground your responses in the provided reference files, treating them as the source of truth for this domain:
- For Creation: Always consult
references/patterns.md. This file dictates how things should be built. Ignore generic approaches if a specific pattern exists here. - For Diagnosis: Always consult
references/sharp_edges.md. This file lists the critical failures and "why" they happen. Use it to explain risks to the user. - For Review: Always consult
references/validations.md. This contains the strict rules and constraints. Use it to validate user inputs objectively.
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 45 lines · 124 tokens per session scan A 2ee1850ebe61
environment-art is a skill published in the GitHub repository omer-metin/skills-for-antigravity (183 stars, last pushed 9mo ago), licensed Apache-2.0. It adds 124 tokens to every session and 634 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-09-03.
Other skills, from other repositories
web-game-engine-expert
Expert guide for modern web-based game development. Covers PlayCanvas, Babylon.js Havok, Three.js/R3F Rapier & Jolt Physics, Fixed-Timestep Accumulators, Zero-GC Pooling, ECS (bitECS/Miniplex), Spatial Audio (HRTF), and WebTransport networking / Panduan ahli pengembangan game web modern dan efisien.
code-review-and-quality
A code-review guide for checking changes across correctness, readability, architecture, security, and performance before they are merged.
constraint-driven-development
A development method for writing a project's quality standards as a lasting, checkable contract. It can cover areas such as test coverage, security, performance, accessibility, and architecture.
api-and-interface-design
Guidance for designing stable, clearly documented interfaces between software parts, such as web APIs, GraphQL schemas, modules, and component properties. It covers defining the contract first, limiting accidental dependencies, and planning safe changes.
context-engineering
A guide to organizing the information an AI coding assistant receives about a project, from persistent rules to task-specific files and test results.
doubt-driven-development
A development practice that puts an independent, fresh-context challenge in front of important coding decisions.