Borrowing it
Nothing to install: this file belongs to unsoldgroup/mail-index. 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/unsoldgroup/mail-index/main/AGENTS.mdgit clone --depth 1 https://github.com/unsoldgroup/mail-indexWrote 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/unsoldgroup/mail-index/agents-md)<a href="https://agentmods.dev/instructions/unsoldgroup/mail-index/agents-md"><img src="https://agentmods.dev/badge/instructions/unsoldgroup/mail-index/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.1 | $0.01379 | $0.01379 |
| Opus 5 | $0.00690 | $0.00690 |
| Sonnet 5 | $0.00276 | $0.00276 |
| Haiku 4.5 | $0.00138 | $0.00138 |
Grade A, and why
mail-index 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 7d 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 — 121 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent setup & usage guide
How to give an AI agent (Claude Desktop, Claude Code, Codex, or any MCP client) recall over a mailbox via mail-index — and how the agent should use it.
mail-index is a stdio MCP server (mail-index-mcp). It is read-only on the
mailbox and operates on a local SQLite index — the agent never gets raw provider
access. Prerequisite: you've installed mail-index and synced at least one account
(see docs/INSTALL.md).
1. Register the MCP server
The server command is mail-index-mcp (the bin) — or, if it isn't on your
client's PATH, an absolute Node + the built entrypoint.
Claude Desktop
Edit ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) /
%APPDATA%\Claude\claude_desktop_config.json (Windows), then restart the app:
{
"mcpServers": {
"mail-index": { "command": "mail-index-mcp" }
}
}
Desktop apps launch with a minimal environment. If the server won't start, or
get_message can't enrich, pin an absolute Node and add the adapter binary's
directory to PATH:
{
"mcpServers": {
"mail-index": {
"command": "/abs/path/to/node",
"args": ["/abs/path/to/mail-index/dist/mcp/index.js"],
"env": { "PATH": "/dir/with/gws:/usr/local/bin:/usr/bin:/bin" }
}
}
}
Claude Code
claude mcp add mail-index -- mail-index-mcp
# or with an absolute path / env:
claude mcp add mail-index --env PATH="/dir/with/gws:/usr/bin:/bin" -- /abs/path/to/node /abs/path/to/mail-index/dist/mcp/index.js
Codex / other MCP clients
Any client that speaks MCP over stdio works — point it at the mail-index-mcp
command (or node dist/mcp/index.js). Use the same env.PATH note as above so
the adapter CLI (e.g. gws) is resolvable for inline body fetches.
Verify: ask the agent "what mail-index tools do you have?" — you should see 23, and "what's the status of my mail index?" should return per-account counts.
2. How the agent should use it
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.
- 7d ago First seen · 121 lines · 1,379 tokens per session scan A db84699c0577
mail-index AGENTS.md is an instructions file published in the GitHub repository unsoldgroup/mail-index (4 stars, last pushed 5d ago), licensed MIT. It adds 1,379 tokens to every session, about $0.0069 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
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.
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.
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).
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.