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 ai-brand-kitgit 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/ai-brand-kit)<a href="https://agentmods.dev/skills/omer-metin/skills-for-antigravity/ai-brand-kit"><img src="https://agentmods.dev/badge/skills/omer-metin/skills-for-antigravity/ai-brand-kit/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/ai-brand-kit"><img src="https://agentmods.dev/badge/skills/omer-metin/skills-for-antigravity/ai-brand-kit.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.00047 | $0.00693 |
| Opus 5.5 | $0.00019 | $0.00277 |
| Sonnet 5.5 | $0.00009 | $0.00139 |
| Haiku 4.5 | $0.00005 | $0.00069 |
Grade A, and why
ai-brand-kit 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 — 32 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ai Brand Kit
Identity
Principles
- {'principle': 'Brand is encoded in prompts, not just documents', 'why': 'AI tools need actionable instructions, not passive PDFs. Every brand\nguideline must translate to reusable prompts that AI can execute.\nDocuments describe; prompts direct.\n'}
- {'principle': 'Consistency requires negative prompts', 'why': 'Telling AI what NOT to generate is as critical as what to generate.\nBrand guardrails prevent style drift. "Never use gradients" is as\nimportant as "Always use bold typography."\n'}
- {'principle': 'Visual style needs reference anchors', 'why': 'AI visual models learn from examples, not descriptions. Create a\ncurated set of 10-20 "brand anchor" images that capture your aesthetic.\nThese become your Midjourney style references and DALL-E training set.\n'}
- {'principle': 'Voice training requires volume', 'why': 'Brand voice emerges from patterns across 50+ examples, not 5. Feed\nAI your best performing copy, tweets, emails. More signal = better\nvoice capture. Quality matters but quantity enables learning.\n'}
- {'principle': 'Governance beats creativity without it', 'why': 'AI generates infinite variations. Without approval workflows and\nversion control, brand chaos ensues. Better to constrain early than\nclean up inconsistency later.\n'}
- {'principle': 'Brand evolves - AI should too', 'why': "Brands aren't static. Your AI training, prompts, and style references\nmust version and evolve. Treat brand assets like code: version control,\nchangelog, deprecation strategy.\n"}
- {'principle': 'Context > generic brand voice', 'why': '"Brand voice" is too broad. You need voice for social, email, docs,\nsupport, landing pages. Context-specific prompts beat one-size-fits-all.\nLinkedIn voice != Twitter voice.\n'}
- {'principle': 'Benchmark quality to prevent drift', 'why': 'Without measurable quality standards, AI output degrades over time.\nDefine 5-10 "gold standard" examples for each content type. New AI\noutput must match or exceed these benchmarks.\n'}
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 · 32 lines · 47 tokens per session scan A b28042b742c1
ai-brand-kit 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 47 tokens to every session and 693 once invoked, about $0.0002 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 skills, from other repositories
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.
performance-optimization
A measurement-first process for improving application speed and responsiveness. It uses profiling—measuring where time is spent—and checks the result again after a change.