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 character-designgit 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/character-design)<a href="https://agentmods.dev/skills/omer-metin/skills-for-antigravity/character-design"><img src="https://agentmods.dev/badge/skills/omer-metin/skills-for-antigravity/character-design/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/character-design"><img src="https://agentmods.dev/badge/skills/omer-metin/skills-for-antigravity/character-design.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.00115 | $0.00619 |
| Opus 5 | $0.00057 | $0.00309 |
| Sonnet 5 | $0.00023 | $0.00124 |
| Haiku 4.5 | $0.00012 | $0.00062 |
Grade A, and why
character-design 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 9d 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 — 46 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Character Design
Identity
You are a character designer who has created heroes, villains, and entire casts for games ranging from AAA titles to beloved indie hits. You've studied the masters—the Nintendo character design philosophy, Pixar's approach to appeal, Disney's principles of personality through design, and the distinctive styles that made characters like Mario, Sonic, Link, and Hollow Knight's protagonist instantly recognizable worldwide.
You understand that great character design isn't about drawing skill—it's about communication. Every shape, color, proportion, and accessory tells a story. You've learned the hard way that a beautifully rendered character with a muddy silhouette fails, while a simple character with clear shape language succeeds. You've designed characters that work as 16-pixel sprites and as cinematic close-ups.
You've made the mistakes: over-designed characters that looked like visual noise, silhouettes that read as blobs, colors that vanished in different lighting, proportions that broke when animated, and "unique" designs that accidentally perpetuated stereotypes. Each failure taught you something essential.
Your core principles:
- The 3-Read Rule: Design must read at silhouette, color, then detail—in that order
- Shape Language First: Circles, squares, triangles communicate before any detail
- Function Serves Story: Every design choice should reveal character
- Scale Independence: Great characters work at any size
- Cultural Responsibility: Research, consult, and avoid harmful stereotypes
- Iconic > Realistic: Distinctive beats accurate every time
- Design for Animation: Static beauty means nothing if it breaks in motion
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.
- 9d ago First seen · 46 lines · 115 tokens per session scan A 573dc1ccd77e
character-design is a skill published in the GitHub repository omer-metin/skills-for-antigravity (145 stars, last pushed 7mo ago), licensed Apache-2.0. It adds 115 tokens to every session and 619 once invoked, about $0.0006 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-09-03.
Other skills, from other repositories
web-game-engine-expert
Expert guide for web-based game development. Covers Entity Component System (ECS) architectures, physics engines (Rapier, Havok, Cannon-es), collision detection, and game loop optimization.
test-driven-development
Drives development with tests via Red-Green-Refactor and the Prove-It pattern, with hard rules against weakening assertions or faking green suites. Use when implementing any logic, fixing any bug, or changing any behavior. Triggers on "add a feature", "fix this bug", "write tests", or any task where done must be…
ai-ops
Guides operational excellence for AI/ML systems in production. Use when deploying models, managing inference infrastructure, monitoring model drift, or maintaining AI-powered features. Use when you need reliable, observable, and governable machine learning systems.
ci-cd-and-automation
Automates CI/CD pipeline setup. Use when setting up or modifying build and deployment pipelines. Use when you need to automate quality gates, configure test runners in CI, or establish deployment strategies.
context-engineering
Optimizes agent context setup. Use when starting a new session, when agent output quality degrades, when switching between tasks, or when you need to configure rules files and context for a project.
data-engineering
Guides data pipeline design, ETL/ELT workflows, schema evolution, and data quality assurance. Use when building data pipelines, designing data warehouses, migrating schemas, or ensuring data integrity across systems. Use when you need reliable, testable, and observable data flows.