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/titanzero/outlook-mcp/claude-mdgit clone --depth 1 https://github.com/titanzero/outlook-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/titanzero/outlook-mcp/claude-md)<a href="https://agentmods.dev/instructions/titanzero/outlook-mcp/claude-md"><img src="https://agentmods.dev/badge/instructions/titanzero/outlook-mcp/claude-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.01299 | $0.01299 |
| Opus 5 | $0.00649 | $0.00649 |
| Sonnet 5 | $0.00260 | $0.00260 |
| Haiku 4.5 | $0.00130 | $0.00130 |
Grade A, and why
outlook-mcp CLAUDE.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 — 107 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
Commands
npm install— always run firstnpm start— start MCP server (stdio transport)npm run auth-server— OAuth server on port 3333 (must be running before auth)npm run inspect— MCP Inspector for interactive testingnpm test— Jest testsnpm run debug— debug: print env vars and start MCP servernpm run find-folders— find folder IDs via Graph APInpm run move-github— move GitHub emails to subfoldernpm run create-rules— create inbox rules for GitHub notificationsnpx kill-port 3333— free port 3333 if occupied
Cursor Rules Map
.cursor/rules/general.mdc— always-apply core conventions (CommonJS, config centralization, baseline response/error/logging patterns).cursor/rules/graph-api.mdc— Graph SDK client usage, fluent API, pagination, and field selection rules.cursor/rules/toon-responses.mdc— TOON data-shaping and formatter usage.cursor/rules/new-tool.mdc— workflow and checklist for adding/registering new tools.cursor/rules/testing.mdc— Jest conventions, mocks, and test structure
Project Structure
index.js — MCP entry point; imports `authTools`, `calendarTools`, `emailTools`, `folderTools`, `rulesTools` and combines them into `TOOLS`
config.js — all constants: field selections, pagination, auth, timezone, response format
outlook-auth-server.js — standalone Express OAuth server
auth/
index.js — exports `authTools`, `ensureAuthenticated`, `tokenManager`
tools.js — auth tool definitions (`about`, `authenticate`, `check-auth-status`)
token-manager.js — token load/save/refresh logic
oauth-server.js — OAuth callback/exchange helpers
email/ — list, search, read, send, mark-as-read + folder-utils.js
calendar/ — list, create, accept, decline, cancel, delete
folder/ — list, create, move
rules/ — list, create, edit-rule-sequence
utils/
graph-client.js — Graph SDK wrapper: `getGraphClient()`, `graphGetPaginated()`
response-formatter.js — TOON / plain-text toggle (reads `config.RESPONSE_FORMAT`)
response-helpers.js — `isAuthError()`, `makeErrorResponse()`, `makeResponse()`
scripts/ — CLI & debug one-off scripts (not imported by app modules)
debug-env.js — debug: print env vars and start MCP server
test-config.js — debug: verify config and token path
find-folder-ids.js — CLI: find folder IDs via Graph API
move-github-emails.js — CLI: move GitHub emails to subfolder
create-notifications-rule.js — CLI: create inbox rules for GitHub
backup-logs.sh — shell: backup Claude Desktop logs
test-direct.sh — shell: test server directly via nc
test-modular-server.sh — shell: test server via MCP Inspector
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 · 107 lines · 1,299 tokens per session scan A 36e887892d4e
outlook-mcp CLAUDE.md is an instructions file published in the GitHub repository titanzero/outlook-mcp (1 stars, last pushed 2mo ago), licensed MIT. It adds 1,299 tokens to every session, about $0.0065 per session on Opus 5. A static security scan graded it A with 0 findings. It comes from a forked repository.
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).
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 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.
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.