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 agentmods add instructions/usejunior/email-agent-mcp/gemini-mdgit clone --depth 1 https://github.com/UseJunior/email-agent-mcpWrote 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/usejunior/email-agent-mcp/gemini-md)<a href="https://agentmods.dev/instructions/usejunior/email-agent-mcp/gemini-md"><img src="https://agentmods.dev/badge/instructions/usejunior/email-agent-mcp/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 | $0.00621 | $0.00621 |
| Opus 5 | $0.00311 | $0.00311 |
| Sonnet 5 | $0.00124 | $0.00124 |
| Haiku 4.5 | $0.00062 | $0.00062 |
Grade A, and why
email-agent-mcp 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 4d 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 — 76 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Email -- Gemini CLI Extension
This extension provides email connectivity for AI agents via one local MCP server.
MCP Server
| Server | Package |
|---|---|
email-agent-mcp |
email-agent-mcp |
Tool Inventory
Reading
| Tool | Description |
|---|---|
list_emails |
List emails in a mailbox folder |
read_email |
Get full content of a single email |
search_emails |
Search emails by query string |
get_mailbox_status |
Check connection status and mailbox warnings |
get_thread |
Retrieve an entire conversation thread |
Sending
| Tool | Description |
|---|---|
send_email |
Compose and send a new email |
reply_to_email |
Reply to an existing email |
Drafts
| Tool | Description |
|---|---|
create_draft |
Create a new draft message |
update_draft |
Update an existing draft |
send_draft |
Send a previously saved draft |
Organization
| Tool | Description |
|---|---|
label_email |
Apply a label or category to an email |
flag_email |
Flag or unflag an email |
mark_read |
Mark an email as read or unread |
move_to_folder |
Move an email to a different folder |
Destructive
| Tool | Description |
|---|---|
delete_email |
Permanently delete an email (requires explicit opt-in) |
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.
- 4d ago First seen · 76 lines · 621 tokens per session scan A c00de5b0d0ef
email-agent-mcp GEMINI.md is an instructions file published in the GitHub repository UseJunior/email-agent-mcp (5 stars, last pushed 2d ago), licensed Apache-2.0. It adds 621 tokens to every session, about $0.0031 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
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).
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.
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.
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).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.