Borrowing it
Nothing to install: this file belongs to larryhudson/simple-notion-mcp-server. 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/larryhudson/simple-notion-mcp-server/main/.github/copilot-instructions.mdgit clone --depth 1 https://github.com/larryhudson/simple-notion-mcp-serverWrote 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/larryhudson/simple-notion-mcp-server/copilot-instructions)<a href="https://agentmods.dev/instructions/larryhudson/simple-notion-mcp-server/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/larryhudson/simple-notion-mcp-server/copilot-instructions.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.00494 | $0.00494 |
| Opus 5 | $0.00247 | $0.00247 |
| Sonnet 5 | $0.00099 | $0.00099 |
| Haiku 4.5 | $0.00049 | $0.00049 |
Grade A, and why
simple-notion-mcp-server 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 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- linear-mcp-server-again copilot-instructions.md — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 42 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project Collaboration Rules
You have access to GitHub tools to help automate and enforce these collaboration rules.
When starting a new task, make sure you are on the main branch and have the latest changes from origin.
Commit Workflow
- Before committing any changes, test them with the user to ensure they are working and do not introduce new errors. Only commit after user confirmation.
- Commit each major step as you go, before proceeding to the next step.
- After each commit, always push to the remote branch to keep the remote in sync.
Issue-Driven Development Workflow
-
All Major Tasks Require Issues
- Every significant feature, bug fix, or change must have a corresponding GitHub issue.
- Issues should be descriptive, outlining the problem, goal, or feature clearly.
-
Work via Pull Requests
- All code changes must be made in branches and submitted as pull requests (PRs).
- Each PR must reference the relevant issue(s) it addresses (e.g., "Closes #issue-number").
- PR titles and descriptions should clearly state the purpose and link to the issue.
-
Blockers, Challenges, and Status Updates
- Any blockers, questions, or status updates must be posted as comments on the relevant issue or pull request.
- If you encounter a blocker or get stuck (e.g., persistent errors, unsolved configuration issues), document the issue as a comment on the relevant GitHub issue or PR, including a summary of what was tried and the current state.
- Use comments to discuss implementation details, request clarification, or provide progress updates.
-
Review and Merge Process
- PRs should be reviewed before merging.
- Only merge PRs after ensuring they address the issue and pass all checks.
-
General Guidelines
- Keep communication clear and concise.
- Reference issues and PRs in all discussions for traceability.
- Update or close issues as work progresses and is completed.
Automation/Assistant Workflow
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 · 42 lines · 494 tokens per session scan A f7073d518ec3
simple-notion-mcp-server copilot-instructions.md is an instructions file published in the GitHub repository larryhudson/simple-notion-mcp-server (1 stars, last pushed 1y ago), licensed MIT. It adds 494 tokens to every session, about $0.0025 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.