Borrowing it
Nothing to install: this file belongs to jmjava/obsidian-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/jmjava/obsidian-mcp/main/.github/copilot-instructions.mdgit clone --depth 1 https://github.com/jmjava/obsidian-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/jmjava/obsidian-mcp/copilot-instructions)<a href="https://agentmods.dev/instructions/jmjava/obsidian-mcp/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/jmjava/obsidian-mcp/copilot-instructions/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/instructions/jmjava/obsidian-mcp/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/jmjava/obsidian-mcp/copilot-instructions.svg" alt="Reviewed on agentmods" width="80" 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.00613 | $0.00613 |
| Opus 5.5 | $0.00245 | $0.00245 |
| Sonnet 5.5 | $0.00123 | $0.00123 |
| Haiku 4.5 | $0.00061 | $0.00061 |
Grade A, and why
obsidian-mcp copilot-instructions.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 23d 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 — 64 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub Copilot: Obsidian Developer Memory
Use the obsidian-dev-memory MCP tools to keep durable engineering memory in the local Obsidian vault. The same server is used by Cursor and Claude. Obsidian does not need to be running.
When to read memory
Call get_project_context before substantial work when prior project memory is likely to help: continuing a feature, debugging a known area, making an architecture change, or explaining why the code is the way it is.
Do not call it for trivial edits.
Call search_memory before guessing about prior decisions. It searches project memory plus top-level TODO/*.md and Daily/*.md. Use read_note only when you already have a vault-relative Markdown path.
When to record sessions
Call capture_work_session after meaningful work:
- an implementation
- an investigation
- a debugging session
- a migration
- an architecture change
- a research task
Do not record:
- typo fixes
- formatting-only changes
- trivial comments
- one-line mechanical edits
Prefer updating today's session note over creating duplicate notes.
When to record decisions
Call record_decision for architectural or engineering decisions that future work should know about, such as:
- selected authentication architecture
- changed API boundaries
- selected persistence mechanism
- changed deployment strategy
- chose one library over another for a durable reason
If a decision file with the same generated name already exists, the server adds a numeric suffix instead of overwriting.
When to update project state
Call update_project_state when the overall project state materially changes. Keep Project State.md concise. It is not a session log. The tool merges a patch: omitted fields keep existing sections, and unknown H2s survive.
When claiming, blocking, unblocking, or finishing a Next Steps, Agent Queue, or TODO/*.md item, prefer list_open_tasks, list_blocked_tasks, claim_task, block_task, unblock_task, and complete_task. They preserve other Project State sections, may check a matching Agent Queue checkbox or update a matching TODO note (claim_task / complete_task only), and do not overwrite daily notes.
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.
- 23d ago Changed · +4 lines · +64 tokens per session e7c91b74e7d6
- 1mo ago Changed · +2 lines · +128 tokens per session 0a659a301704
- 2mo ago Changed · +2 tokens per session 11ce585c007f
- 2mo ago First seen · 58 lines · 419 tokens per session scan A 7ba52635ee7f
obsidian-mcp copilot-instructions.md is an instructions file published in the GitHub repository jmjava/obsidian-mcp (1 stars, last pushed 23d ago), licensed MIT. It adds 613 tokens to every session, about $0.0025 per session on Opus 5.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).
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.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
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 copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deepseek-harness AGENTS.md
AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.