Borrowing it
Nothing to install: this file belongs to dovrosenberg/onenote-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/dovrosenberg/onenote-mcp/main/CLAUDE.mdgit clone --depth 1 https://github.com/dovrosenberg/onenote-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/dovrosenberg/onenote-mcp/claude-md)<a href="https://agentmods.dev/instructions/dovrosenberg/onenote-mcp/claude-md"><img src="https://agentmods.dev/badge/instructions/dovrosenberg/onenote-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.02117 | $0.02117 |
| Opus 5 | $0.01059 | $0.01059 |
| Sonnet 5 | $0.00423 | $0.00423 |
| Haiku 4.5 | $0.00212 | $0.00212 |
Grade A, and why
onenote-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 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 — 143 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
Working notes for agents in this repository. project-spec.md is the authoritative
design document — read the relevant section of it before changing behaviour.
api-overview.md is what Microsoft Graph's OneNote endpoints actually do: the resource
paths, the query options and their limits, and the places the service contradicts its own
documentation. Read it before adding or changing a Graph call, and add anything new that
a live run reveals.
The conventions are split by area. Each file states what it covers; read the one whose area you are changing, because most of its rules exist to stop a specific silent failure.
| File | Read it before changing |
|---|---|
docs/graph.md |
any Microsoft Graph call, the request budget, throttling, or the token cache |
docs/mirror.md |
anything under src/mirror-*.ts, src/read-sync.ts, or the sync route |
docs/content.md |
ink rendering, the HTML trimmer, page reads or writes, the name-lookup ladder |
docs/server.md |
src/server.ts, the MCP transport, OAuth, the keepalive route, src/logging.ts |
docs/config-deploy.md |
a configuration variable, startup behaviour, the Dockerfile, deploy.yml |
test/README.md |
any test file — what each suite asserts and what it deliberately does not |
Directory structure
onenote-mcp/
├── src/ # TypeScript source, the only thing that ships│
├── test/ # node --test suites; test/<name>.test.ts covers src/<name>.ts
│ ├── README.md # what each suite covers, and what it deliberately does not
│ ├── fixtures/ # hand-authored InkML and HTML; never a captured page dump
├── docs/ # area conventions; see the table above
├── scripts/ # operational shell scripts, not part of the built artifact
│ └── test/ # bash tests, run by scripts/test/run.sh
├── .github/workflows/ # deploy.yml, the only CI; builds, tests, pushes, deploys
└── dist/ # build output; gitignored, never edited, never committed
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 · 143 lines · 2,117 tokens per session scan A b912048ccf4f
onenote-mcp CLAUDE.md is an instructions file published in the GitHub repository dovrosenberg/onenote-mcp (0 stars, last pushed 17d ago), licensed MIT. It adds 2,117 tokens to every session, about $0.0106 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.