bear-notes-mcp copilot-instructions.md

Instructions for reviewing code changes and developing features in the bear-notes-mcp project. They describe which project documents to read and how to give specific, evidence-based feedback.

In plain words
What is it for?
Reviewing pull requests and planning new features while checking project specifications, code style, simplicity, and existing changes.
Why use it?
They provide a consistent review process and help avoid recommendations that conflict with the project's design or coding rules.

Instructions file for GitHub Copilot

Install

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.

agentmods
npx agentmods add instructions/vasylenko/bear-notes-mcp/copilot-instructions
Clone the repo
git clone --depth 1 https://github.com/vasylenko/bear-notes-mcp

Made for: GitHub Copilot.

Per session 279 This file is loaded in full into every session.
When invoked 279 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00279 $0.00279
Opus 5 $0.00139 $0.00139
Sonnet 5 $0.00056 $0.00056
Haiku 4.5 $0.00028 $0.00028

Measured 2d ago against content hash ab120d586b39, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

bear-notes-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 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.

.github/copilot-instructions.md · 25 lines

What it actually says

When performing a code review for a PR

Review Objective

  • Perform the PR review as instructed in the "Review Guidelines" section below.
  • Be specific, concise, and actionable in your feedback.
  • Explain the "why" behind your recommendations. Never assume — only state what you know for sure based on the new code you review and the existing codebase.

Review Guidelines

  1. Review for KISS and DRY
  • Carefully read the docs/dev/SPECIFICATION.md file, which explains the system architecture and design constraints (including KISS/YAGNI principles) for this project.
  • Using this knowledge, diligently review the PR changes according to these principles.
  1. Review for Codestyle
  • Carefully read the docs/dev/CODE_STYLE.md file, which explains the style rules of this project.
  • Using this knowledge, diligently review the PR changes according to the style guides.

When working on a new feature or an idea

  1. Start from carefully reading the CLAUDE.md and README.md documents to get the context of this project
  2. Then, read the docs/dev/SPECIFICATION.md document to deep dive into the technical details
  3. Then, read the CHANGELOG.md to know what has been already shipped
  4. IMPORTANT! Only after completion of those three steps, you may start working on a new feature requested by the user.
Changes

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.

  1. 2d ago First seen · 25 lines · 279 tokens per session scan A ab120d586b39

Subscribe to this mod's changes

bear-notes-mcp copilot-instructions.md is an instructions file published in the GitHub repository vasylenko/bear-notes-mcp (206 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 279 tokens to every session, about $0.0014 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.