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/mspstack/mcp-planner/claude-mdgit clone --depth 1 https://github.com/mspstack/mcp-plannerWhat 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.01052 | $0.01052 |
| Opus 5 | $0.00526 | $0.00526 |
| Sonnet 5 | $0.00210 | $0.00210 |
| Haiku 4.5 | $0.00105 | $0.00105 |
Grade A, and why
mcp-planner 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 2d 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 — 63 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
MCP server for Microsoft Planner via Microsoft Graph. Sibling project to mcp-connectwise-psa (copied from it) and mcp-itglue — same architecture.
Commands
npm run build— tsc to dist/npm test— vitestnpm run dev/npm run dev:http— tsx, stdio or HTTP transportnpm run bundle— build the Claude Desktop.mcpb
Architecture
src/index.ts— CLI entry;--transport stdio|http,--port; USAGE textsrc/config.ts—loadConfig(argv, env)→ServerConfig;ConfigError; MS_* env varssrc/server.ts—createServer(session)builds a per-sessionMcpServer;INSTRUCTIONSstringsrc/graph/client.ts—GraphClient: client-credentials token (cached, 60s skew),get/getList/post/patch/delete; PATCH/DELETE take an explicitetag(If-Match); PATCH sendsPrefer: return=representation;GraphApiError+describeErrorsrc/graph/types.ts— Graph resource shapes;priorityLabel/PRIORITY_VALUES/progressLabelsrc/http/app.ts— Express app; BYOK viax-ms-tenant-id/x-ms-client-id/x-ms-client-secretheaders with fallback to server env creds; session principal pinned by SHA-256 hashsrc/tools/registrar.ts—ToolRegistrar; no MCP-level role gating (Graph is the access control)src/tools/shared.ts— zod fragments (responseFormatField,topField),text/failure/json/clipsrc/tools/{groups,plans,tasks}.ts—planner_*tools;plans.tsincludesplanner_list_my_plans(/me/planner/plansdelegated,/users/{id}/planner/planswith user_id)src/tools/session.ts—planner_whoami: app-only vs delegated (+ acting user via/me); mode detection isGraphClient.isDelegatedsrc/tools/advanced.ts— opt-in escape hatch (PLANNER_ADVANCED_TOOLSET=true/--advanced, off by default):graph_get(read-only GET via the verb-lockedGraphClient.get, allowlisted to/planner,/groups,/users— plus/meon delegated sessions;/betarejected; a pasted@odata.nextLinkworks aspath— its inline query is parsed and merged, structured args win) andgraph_find_endpoint(lexical search over the hand-maintainedsrc/reference/graph-endpoints.ts). Search functions kept in sync with mcp-connectwise-psa'sadvanced.ts
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.
- 2d ago Changed · +8 lines · +195 tokens per session 57d9358eb6d6
- 2d ago First seen · 55 lines · 857 tokens per session scan A 64469fe5aaee
mcp-planner CLAUDE.md is an instructions file published in the GitHub repository mspstack/mcp-planner (4 stars, last pushed 2d ago), licensed MIT. It adds 1,052 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.