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/ahmadzafar-code/emailsrboring/agents-mdgit clone --depth 1 https://github.com/ahmadzafar-code/emailsRboringWhat 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.01064 | $0.01064 |
| Opus 5 | $0.00532 | $0.00532 |
| Sonnet 5 | $0.00213 | $0.00213 |
| Haiku 4.5 | $0.00106 | $0.00106 |
Grade A, and why
emailsRboring 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 yesterday.
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 — 64 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
Briefing for AI coding agents working on emailsRboring-mcp. Humans: start with README.md; this file holds the build/test commands, invariants, and gotchas an agent needs to change the code safely.
What this is
A redacting policy proxy (one MCP server) that fronts two upstream Apple Mail MCP servers and adds the safety layer:
imdinu/apple-mail-mcp(Python) → read/search. Spawned read-only (serve -r).sweetrb/apple-mail-mcp(TypeScript) → write/organize/send.
The proxy spawns both as stdio child processes, merges their tools behind a fail-closed allowlist, routes calls, and redacts every response. It is macOS-only (Apple Mail).
Architecture (where things live)
| File | Responsibility |
|---|---|
src/index.ts |
Entry point. Low-level Server + StdioServerTransport; ListTools/CallTool handlers; loads emailsRboring.config.json. |
src/upstreams.ts |
Spawns imdinu + sweetrb via StdioClientTransport. Reads EMAILSRBORING_IMDINU_CMD / EMAILSRBORING_SWEETRB_ENTRY. |
src/allowlist.ts |
The fail-closed allowlist + tool-name normalization (mail_*) + annotations + confirm injection. |
src/router.ts |
Dispatch, send-gate, draft-forcing, id String(), attachment-exfil block, untrusted-content fence. |
src/redact.ts |
The single redaction chokepoint (redactToolResult): strips structuredContent, masks OTPs/codes, truncates at 25k chars. |
verify.py |
22-check end-to-end verification (surface, redaction, send-gate, exfil). |
Build / run / verify
npm install
npm run build # tsc → build/
# the proxy REQUIRES these env vars (see README for what they point at):
export EMAILSRBORING_IMDINU_CMD=/abs/path/to/apple-mail-mcp
export EMAILSRBORING_SWEETRB_ENTRY=/abs/path/to/sweetrb/build/index.js
node build/index.js # boots; prints "[emailsRboring] ready — 26 tools"
python3 verify.py # MUST stay 22/22 ALL GREEN before any commit
npm run build must exit 0 with no any introduced; tsconfig.json is strict.
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.
- yesterday First seen · 64 lines · 1,064 tokens per session scan A fb7456c58071
emailsRboring AGENTS.md is an instructions file published in the GitHub repository ahmadzafar-code/emailsRboring (0 stars, last pushed 2mo ago), licensed MIT. It adds 1,064 tokens to every session, about $0.0053 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.