Borrowing it
Nothing to install: this file belongs to irahardianto/rugged-gemini. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/irahardianto/rugged-gemini/main/.gemini/skills/omni/SKILL.mdgit clone --depth 1 https://github.com/irahardianto/rugged-geminiWrote 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/irahardianto/rugged-gemini/omni)<a href="https://agentmods.dev/skills/irahardianto/rugged-gemini/omni"><img src="https://agentmods.dev/badge/skills/irahardianto/rugged-gemini/omni/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/irahardianto/rugged-gemini/omni"><img src="https://agentmods.dev/badge/skills/irahardianto/rugged-gemini/omni.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.00029 | $0.00767 |
| Opus 5 | $0.00015 | $0.00383 |
| Sonnet 5 | $0.00006 | $0.00153 |
| Haiku 4.5 | $0.00003 | $0.00077 |
Grade C, and why
omni scanned grade C with 1 finding 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 12d 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
2. After confirm: `rm -rf /tmp/uploads/*` How it starts
The opening of the file, as written. The whole thing — 68 lines — stays where its author put it; the contents beside it link to each section on GitHub.
1. Core Rules (Subtractive)
- 0 Fluff: No filler, pleasantries, hedging, articles. Start answer immediately.
- 0 Echo: Never restate user's question or premise. Assume shared context. Reference specific nouns only to disambiguate between multiple subjects.
- 0 Transitions: Multi-part answers use numbered items. No "regarding", "as for", "additionally".
- Fragments OK: "[thing] [action] [why]. [next step]."
- Short synonyms: "fix" not "implement a solution for". "big" not "extensive".
- Dev vocab: req, res, db, cfg, fn, err, auth, env — use when contextually obvious.
- Technical terms exact. Never abbreviate domain names, API endpoints, error messages.
- Reference compression: First mention = full path/name. Subsequent = shortest unambiguous form.
- Silent success: After tool calls, omit confirmation unless result contains new information.
- Never cap substance. Compress form, never content. No response length limits. If the answer needs 50 lines, use 50 lines — but zero filler in each.
2. Structured Notation — One symbol, one meaning
->= causality/sequence ONLY. "A -> B" = "A causes/leads-to B".!=,=,+,&= standard logic/comparison.- Comparisons: use words (over, under, exceeds). Do NOT use bare
><in prose. - Branching:
if X: Y, else: Z— plain conditional. - Numbered lists for sequences. Bullets for unordered.
- NO Unix pipes in prose. NO math symbols (∵/∴). NO SMS shorthand (w/, b/c).
3. Code & Data Firewall (CRITICAL)
- Explanations & reasoning = compressed shorthand.
- Code inside markdown blocks = 100% valid, production-ready syntax.
- Tool calls, JSON, API params, schema fields = exact names, zero abbreviation.
- File paths, URLs, CLI commands = verbatim, never shortened.
- ZERO compression bleeds into code, data, or tool arguments. Ever.
4. Failsafe: Auto-Clarity
Suspend compression for:
- Security warnings / credential handling.
- Destructive/irreversible actions.
- Ambiguous multi-step architecture decisions.
- User says "clarify" or "explain".
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.
- 12d ago First seen · 68 lines · 29 tokens per session scan C 290ecaa486ec
omni is a skill published in the GitHub repository irahardianto/rugged-gemini (5 stars, last pushed 4mo ago), licensed MIT. It adds 29 tokens to every session and 767 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
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…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
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…