Borrowing it
Nothing to install: this file belongs to jleechanorg/mcp_mail. 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/jleechanorg/mcp_mail/main/GEMINI.mdgit clone --depth 1 https://github.com/jleechanorg/mcp_mailWrote 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/jleechanorg/mcp_mail/gemini-md)<a href="https://agentmods.dev/instructions/jleechanorg/mcp_mail/gemini-md"><img src="https://agentmods.dev/badge/instructions/jleechanorg/mcp_mail/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/jleechanorg/mcp_mail/gemini-md"><img src="https://agentmods.dev/badge/instructions/jleechanorg/mcp_mail/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.00752 | $0.00752 |
| Opus 5.5 | $0.00301 | $0.00301 |
| Sonnet 5.5 | $0.00150 | $0.00150 |
| Haiku 4.5 | $0.00075 | $0.00075 |
Grade A, and why
mcp_mail 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 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 — 55 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Gemini Agent Protocol
Mandatory Context
You must locate and internalize the following project documentation before taking action:
-
CLAUDE.md(in project root):- Contains the authoritative coding standards, testing commands, and architectural patterns.
- INSTRUCTION: Read this file immediately. Strict adherence to its testing policies (e.g.,
TESTING=true) and code style is mandatory.
-
AGENTS.md(if present):- Describes the agent ecosystem and roles.
- INSTRUCTION: Check for this file to understand broader system context.
Critical Protocol: Push & Deploy Verification
NEVER report a git push or deployment as "Complete" or "Success" based on a RUNNING status.
- Wait for Termination: You MUST wait for the command to fully terminate.
- Verify Exit Code: You MUST verify the
Exit codeis0. - Verify Output: You MUST see the confirmation output (e.g.,
To https://github.com...,Resolving deltas, orDeployed to...). - Report Failures: If hooks fail (even pre-push or pre-commit hooks), report the failure details immediately. Do NOT assume success.
Operational Rules
1. Test Isolation
- Respect Flags: Never ignore testing flags like
TESTING=true. - Mock Mode: Ensure tests run in mock mode to avoid hitting production services unless explicitly running an end-to-end integration suite against a test environment.
2. Verify Before Action
- State check: Use
grep,ls, orview_fileto confirm code state before editing. Do not rely on assumptions or memory of previous turns.
3. Logic Preservation
- Conflict Resolution: When resolving conflicts, analyze the intent of both sides. Do not blindly discard validation logic (e.g.,
try/exceptblocks, parameter parsing) or architectural changes.
4. Efficient Testing
- Targeted Execution: Do not run all tests via
run_tests.shindiscriminately, as it may take too long. - Preferred Command: Run only relevant tests using
uv run pytest <path/to/test>.
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 · 55 lines · 752 tokens per session scan A 1e3dbc9dbf9e
mcp_mail GEMINI.md is an instructions file published in the GitHub repository jleechanorg/mcp_mail (11 stars, last pushed 2mo ago), licensed MIT. It adds 752 tokens to every session, about $0.0030 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 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.