Borrowing it
Nothing to install: this file belongs to JhonatanRian/gemini-simplify-extension. 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/JhonatanRian/gemini-simplify-extension/main/GEMINI.mdgit clone --depth 1 https://github.com/JhonatanRian/gemini-simplify-extensionWrote 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/instructions/jhonatanrian/gemini-simplify-extension/gemini-md)<a href="https://agentmods.dev/instructions/jhonatanrian/gemini-simplify-extension/gemini-md"><img src="https://agentmods.dev/badge/instructions/jhonatanrian/gemini-simplify-extension/gemini-md.svg" alt="Measured on agentmods" 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.00420 | $0.00420 |
| Opus 5 | $0.00210 | $0.00210 |
| Sonnet 5 | $0.00084 | $0.00084 |
| Haiku 4.5 | $0.00042 | $0.00042 |
Grade A, and why
gemini-simplify-extension GEMINI.md 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 6d 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
Gemini Simplify — Extension Context
You have access to the Gemini Simplify extension, an elite polyglot code simplification system.
Available Command
/simplify— Executes intelligent, ecosystem-aware code simplification using parallel specialized agents.- Usage:
/simplify(analyzes recent git diffs) or/simplify <scope>(targets specific files/directories).
- Usage:
Available Sub-Agents
You can delegate tasks to 4 specialized architect agents. Invoke them using @agent_name:
| Agent | Expertise |
|---|---|
@abstraction |
Code reuse, duplication detection, standard library enforcement |
@clarity |
Readability, naming, cyclomatic complexity reduction, clean code |
@performance |
Algorithmic efficiency, concurrency, memory leaks, N+1 queries |
@standards |
Version-specific idioms, type safety, modern syntax, framework guidelines |
Workflow
When the user invokes /simplify, follow this orchestration:
- Phase 0 — Detect: Scan manifests and lockfiles to identify the exact language, framework, and version in use.
- Phase 1 — Research: Use
google_web_searchto ground yourself in the official documentation for the detected stack. Never guess modern syntax. - Phase 2 — Dispatch: Invoke
@abstraction,@clarity,@performance, and@standardsin parallel on the target code. - Phase 3 — Synthesize: Aggregate findings, discard false positives, apply fixes, and present an architectural summary to the user.
Rules
- Never assume the stack. Always detect it from project files first.
- Evidence-based only. If unsure about a modern API, search the web before suggesting it.
- Action-oriented. Apply fixes directly — don't just comment on problems.
- Respect user consent. Present the plan and wait for authorization before applying destructive changes.
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.
- 6d ago First seen · 36 lines · 420 tokens per session scan A a164bee0e45a
gemini-simplify-extension GEMINI.md is an instructions file published in the GitHub repository JhonatanRian/gemini-simplify-extension (1 stars, last pushed 4mo ago), licensed MIT. It adds 420 tokens to every session, about $0.0021 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-08-31.
Other instructions, from other repositories
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.