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/tecnologicachile/mail-mcp/agents-mdgit clone --depth 1 https://github.com/tecnologicachile/mail-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/tecnologicachile/mail-mcp/agents-md)<a href="https://agentmods.dev/instructions/tecnologicachile/mail-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/tecnologicachile/mail-mcp/agents-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.01919 | $0.01919 |
| Opus 5 | $0.00959 | $0.00959 |
| Sonnet 5 | $0.00384 | $0.00384 |
| Haiku 4.5 | $0.00192 | $0.00192 |
Grade A, and why
mail-mcp AGENTS.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 5d 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 — 244 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
Guidance for coding agents working in mail-mcp.
Project Snapshot
- Language: Rust (edition
2024) - Runtime:
tokio - Protocol framework:
rmcp - Domain: IMAP-backed MCP server over stdio
- Entry point:
src/main.rs - Main server implementation:
src/server.rs
Cursor/Copilot Rules
No repository-specific Cursor or Copilot instruction files were found:
.cursorrules: not present.cursor/rules/: not present.github/copilot-instructions.md: not present
If these are added later, treat them as higher-priority local policy and merge them into this file.
Build, Lint, and Test Commands
Run commands from repo root.
Build
- Debug build:
cargo build - Release build:
cargo build --release
Format
- Check formatting:
cargo fmt -- --check - Apply formatting:
cargo fmt
Lint
- Strict clippy (all targets):
cargo clippy --all-targets -- -D warnings
Test
- Run all tests:
cargo test - List tests:
cargo test -- --list - GreenMail integration smoke test:
scripts/test-greenmail.sh
Run a Single Test
Use a test name substring:
cargo test parses_mailbox_with_colonscargo test pagination::tests::evicts_to_max_entries
Run a single test and show stdout:
cargo test parses_mailbox_with_colons -- --exact --nocapturecargo test greenmail_imap_smoke_test -- --exact --ignored --nocapture
Run tests in one module/file scope:
cargo test message_id::testscargo test mime::testscargo test pagination::tests
Suggested Local Validation Sequence
Before finalizing changes, run:
cargo fmt -- --checkcargo clippy --all-targets -- -D warningscargo test
Do not skip clippy or tests for code changes.
Docker
The repository includes a minimal multi-stage Dockerfile for running the MCP server.
Build and Run
- Build image:
docker build -t mail-mcp . - Run over stdio:
docker run --rm -i --env-file .env mail-mcp
Docker Notes for Agents
- Keep MCP transport as stdio (do not add HTTP listener behavior by default).
- Keep runtime image minimal (current pattern: builder image +
scratch). - If dependencies require a non-scratch runtime, document why in the PR/commit message.
- Keep
.dockerignorealigned with repo layout to avoid leaking local files and reduce context size. - Docker publish workflow:
.github/workflows/publish-docker.yml. - Docker publish trigger: git tags matching
v*.*.*. - Published image tags include
latest,vX.Y.Z, andX.Y.Zon GHCR.
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.
- 5d ago First seen · 244 lines · 1,919 tokens per session scan A c5f526e8021a
mail-mcp AGENTS.md is an instructions file published in the GitHub repository tecnologicachile/mail-mcp (73 stars, last pushed 3d ago), licensed MIT. It adds 1,919 tokens to every session, about $0.0096 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-30.
Other instructions, from other repositories
cli AGENTS.md
AGENTS.md instructions for googleworkspace/cli, covering agents.md, project overview, build & test, changesets and architecture.
turso AGENTS.md
Instructions for tursodatabase/turso, covering turso agent guidelines, quick reference, testing, running tests and test organization.
intelligent-terminal rust.instructions.md
Concise Rust coding conventions for this repository.
azure-sdk-for-rust resourcemanager.instructions.md
Instructions for Azure/azure-sdk-for-rust, a project described as: This repository is for the active development of the Azure SDK for Rust. For consumers of the SDK we recommend visiting Docs.rs and looking up the docs for any of libraries in the SDK.
iroha AGENTS.md
AGENTS.md instructions for hyperledger-iroha/iroha, covering agents instructions, quickstart, repository structure, development workflow and documentation.
bifrost AGENTS.md
Instructions for bifrost-proxy/bifrost, covering bifrost 项目开发规则, 执行心法, 执行模式与完成定义, 任务模式判定 and 变更类型与验证路由(先判定,后执行).