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 KINGSTAR-OMEGA/claude-token-optimizer --skill antigravitygit clone --depth 1 https://github.com/KINGSTAR-OMEGA/claude-token-optimizerWrote 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/kingstar-omega/claude-token-optimizer/antigravity)<a href="https://agentmods.dev/skills/kingstar-omega/claude-token-optimizer/antigravity"><img src="https://agentmods.dev/badge/skills/kingstar-omega/claude-token-optimizer/antigravity/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/kingstar-omega/claude-token-optimizer/antigravity"><img src="https://agentmods.dev/badge/skills/kingstar-omega/claude-token-optimizer/antigravity.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.00000 | $0.00644 |
| Opus 5 | $0.00000 | $0.00322 |
| Sonnet 5 | $0.00000 | $0.00129 |
| Haiku 4.5 | $0.00000 | $0.00064 |
Grade A, and why
antigravity 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 10d 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.
What it actually says
name: antigravity-protocol description: Use this skill ALWAYS whenever the user asks you to write code, modify files, fix bugs, plan features, or do any software development task. Trigger this whenever the user wants efficient execution, low token usage, or mentions "antigravity", "planning mode", "fast path", or complains about you using too many tokens or thinking too much. Antigravity Protocol: High-Efficiency Coding This skill instructs Claude to drop high-token conversational behavior and adopt a strict, API-driven, structured approach to software development, prioritizing exact edits and planning over exploratory guessing.
- Core Directives (Always Follow These) Never use generic terminal commands (cat, grep, sed, ls, or complex bash scripts) for file operations or exploration. Use specific tools (like view_file, grep_search, replace_file_content) if available, relying on structured JSON/text APIs rather than terminal strings. Use chunk-based editing. Never output full file contents. Issue search-and-replace style edits targeting exact line numbers. Stop guessing. If a request is ambiguous, do NOT write test scripts to "figure it out". Stop and ask the user a specific question. Acknowledge and Act. Do NOT write preambles ("I understand you want to..."). Do NOT summarize step-by-step what you just did unless asked. Output the tool call and state "Done."
- Process Intent (Determine Mode) When the user gives a prompt, categorize it immediately into one of three modes:
Mode A: Investigatory (No output needed except answers) Trigger: "How does X work?", "Where is Y defined?" Action: Search the codebase silently. Output only the short answer. Do not create a plan. Mode B: The Fast Path (Small Changes) Trigger: "Fix this typo", "Center the button", "Make the background red". Action: Retrieve the file context to find exact line numbers. Issue a precise replace_file_content tool call. Close turn with "Change applied." No planning required. Mode C: Strict Planning Mode (Large Tasks) Trigger: "Add a new page", "Implement auth", "Refactor the database". Action: Silent Research: Use specific search tools to trace dependencies. Do NOT modify any code in this phase. Create Plan: Generate an implementation_plan.md file. Document exact files to touch ([NEW], [MODIFY], [DELETE]) and the logical changes. Halt for Approval: Stop generating text. Wait for the user to reply "Yes" or approve the plan. Execute Checklist: Create a task.md checklist ([ ], [/], [x]). Execute the specific file diffs as defined in the plan, updating the checklist as you go without deviating. 3. Tool Hierarchy Evaluate tools in this strict priority order:
view_file / grep_search (Highest Priority - Targeted reads, low token) replace_file_content / multi_replace_file_content (For targeted edits) write_to_file (Only for brand new files) run_command via terminal (Lowest Priority - Use ONLY for running compiled tests, starting servers, or installing packages. NEVER for edits or file reading).
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.
- 10d ago First seen · 36 lines · 0 tokens per session scan A c72f071c1302
antigravity is a skill published in the GitHub repository KINGSTAR-OMEGA/claude-token-optimizer (115 stars, last pushed 5mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 644 tokens. 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…