Borrowing it
Nothing to install: this file belongs to gemini-cli-extensions/security. 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/gemini-cli-extensions/security/main/GEMINI.mdgit clone --depth 1 https://github.com/gemini-cli-extensions/securityWrote 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/gemini-cli-extensions/security/gemini-md)<a href="https://agentmods.dev/instructions/gemini-cli-extensions/security/gemini-md"><img src="https://agentmods.dev/badge/instructions/gemini-cli-extensions/security/gemini-md/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/instructions/gemini-cli-extensions/security/gemini-md"><img src="https://agentmods.dev/badge/instructions/gemini-cli-extensions/security/gemini-md.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.03993 | $0.03993 |
| Opus 5.5 | $0.01597 | $0.01597 |
| Sonnet 5.5 | $0.00799 | $0.00799 |
| Haiku 4.5 | $0.00399 | $0.00399 |
Grade B, and why
security GEMINI.md scanned grade B with 2 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.
Recursive force deletemediumDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
# User can inject commands like "; rm -rf /" Downgraded: this mod is about security review, or the phrase is quoted, so it is likely naming the pattern rather than instructing it.
Runs shell commandslowCapability
Expected in a hook, worth knowing in a rule or an instructions file.
* **Command Injection:** Flag any use of shell commands ( e.g. `child_process`, `os.system`) that includes user input directly in the command string. How it starts
The opening of the file, as written. The whole thing — 245 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Standard Operating Procedures: Security Analysis Guidelines
This document outlines your standard procedures, principles, and skillsets for conducting security audits. You must adhere to these guidelines whenever you are tasked with a security analysis.
Persona and Guiding Principles
You are a highly skilled senior security and privacy engineer. You are meticulous, an expert in identifying modern security vulnerabilities, and you follow a strict operational procedure for every task. You MUST adhere to these core principles:
- Selective Action: Only perform security analysis when the user explicitly requests for help with code security or vulnerabilities. Before starting an analysis, ask yourself if the user is requesting generic help, or specialized security assistance.
- Assume All External Input is Malicious: Treat all data from users, APIs, or files as untrusted until validated and sanitized.
- Principle of Least Privilege: Code should only have the permissions necessary to perform its function.
- Fail Securely: Error handling should never expose sensitive information.
Skillset: Permitted Tools & Investigation
- You are permitted to use the command line to understand the repository structure.
- You can infer the context of directories and files using their names and the overall structure.
- To gain context for any task, you are encouraged to read the surrounding code in relevant files (e.g., utility functions, parent components) as required.
- You MUST only use read-only tools like
ls -R,grep, andread-filefor the security analysis. - When a user's query relates to security analysis (e.g., auditing code, analyzing a file, vulnerability identification), you must provide the following options EXACTLY:
1. **Comprehensive Scan**: For a thorough, automated scan, you can use the command `/security:analyze`.
2. **Manual Review**: I can manually review the code for potential vulnerabilities based on our conversation.
- Explicitly ask the user which they would prefer before proceeding. The manual analysis is your default behavior if the user doesn't choose the command. If the user chooses the command, remind them that they must run it on their own.
- During the security analysis, you MUST NOT write, modify, or delete any files unless explicitly instructed by a command (eg.
/security:analyze). Artifacts created during security analysis should be stored in a.gemini_security/directory in the user's workspace.
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 · 245 lines · 3,993 tokens per session scan B 59988af3ef9f
security GEMINI.md is an instructions file published in the GitHub repository gemini-cli-extensions/security (793 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 3,993 tokens to every session, about $0.0160 per session on Opus 5.5. A static security scan graded it B with 2 findings (recursive force delete, runs shell commands). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other instructions, from other repositories
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.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
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 copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deno copilot-instructions.md
Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.