Borrowing it
Nothing to install: this file belongs to desek/outlook-local-mcp. 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/desek/outlook-local-mcp/main/AGENTS.mdgit clone --depth 1 https://github.com/desek/outlook-local-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/desek/outlook-local-mcp/agents-md)<a href="https://agentmods.dev/instructions/desek/outlook-local-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/desek/outlook-local-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.1 | $0.05499 | $0.05499 |
| Opus 5 | $0.02750 | $0.02750 |
| Sonnet 5 | $0.01100 | $0.01100 |
| Haiku 4.5 | $0.00550 | $0.00550 |
Grade A, and why
outlook-local-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 8d 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 — 381 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
- Don't be an overachiever. Focus on the task, aiming for perfection in the execution rather than in adding extras.
- Implement the solution using many small, isolated, single-purpose files. Your primary goal is to minimize the Lines of Code (LoC) in each file. Code duplication is explicitly allowed to maintain this structure.
- Follow the Architectural Governance and Project Requirements Change process.
- Use
deepwikiMCP for knowledge about specific package implementations details when needed. - Use the file
.deepwikias a repository for relevant DeepWiki repositories. - Continuously keep the
.gitignoreaccurate to not bloat the repository. CHANGELOG.mdis managed by release-please and MUST NOT be manually updated.
Project Structure
The project follows the Go standard project layout (see CR-0021):
outlook-mcp/
cmd/
outlook-local-mcp/
main.go # Entry point: config load, subsystem init, lifecycle
internal/
config/ # Config struct, LoadConfig, ValidateConfig
auth/ # Browser/device code auth, token cache, auth record, account registry, account resolver
logging/ # InitLogger, SanitizingHandler, PII masking, MultiHandler, file logging
audit/ # Audit logging subsystem, AuditWrap middleware
graph/ # Graph API utilities: errors, retry, timeout, serialization, enums, recurrence
validate/ # Input validation helpers
observability/ # OpenTelemetry metrics and tracing, WithObservability middleware
buildinfo/ # Build identity and host environment snapshot (system.about; CR-0067)
server/ # RegisterTools, ReadOnlyGuard, AwaitShutdownSignal
tools/ # The 4 aggregate domain tools and their verb registries
docs/
...
Build: go build ./cmd/outlook-local-mcp/
Install: go install github.com/desek/outlook-local-mcp/cmd/outlook-local-mcp@latest
New code must be placed in the appropriate internal/ package, not the repository root.
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.
- 8d ago First seen · 381 lines · 5,499 tokens per session scan A bb1c6180d17d
outlook-local-mcp AGENTS.md is an instructions file published in the GitHub repository desek/outlook-local-mcp (41 stars, last pushed yesterday), licensed MIT. It adds 5,499 tokens to every session, about $0.0275 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
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.