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/sammorrowdrums/remarkable-mcp/copilot-instructionsgit clone --depth 1 https://github.com/SamMorrowDrums/remarkable-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/sammorrowdrums/remarkable-mcp/copilot-instructions)<a href="https://agentmods.dev/instructions/sammorrowdrums/remarkable-mcp/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/sammorrowdrums/remarkable-mcp/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 | $0.01893 | $0.01893 |
| Opus 5 | $0.00946 | $0.00946 |
| Sonnet 5 | $0.00379 | $0.00379 |
| Haiku 4.5 | $0.00189 | $0.00189 |
Grade A, and why
remarkable-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 4d 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 — 262 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Copilot Instructions for remarkable-mcp
Project Overview
This is an MCP (Model Context Protocol) server that provides access to reMarkable tablet data. It's a Python project using MCP Python SDK 2.x MCPServer.
Git Workflow
Always work on feature branches and submit PRs. Never push directly to main.
# Create a feature branch
git checkout -b feature/my-feature
# After making changes, push and create PR
git push origin feature/my-feature
# Then create PR via GitHub
Branch protection is enabled on main - all changes must go through pull requests with passing CI checks.
Package Management
Always use uv for all package management operations.
# Install dependencies
uv sync
# Install with dev dependencies
uv sync --extra dev
# Add a new dependency
uv add <package>
# Add a dev dependency
uv add --dev <package>
Never use:
pip installdirectlypip freezepoetry
Running Tests
Always run tests with:
uv run pytest -v
For specific test patterns:
# Run specific test class
uv run pytest -v -k "TestClassName"
# Run with coverage
uv run pytest -v --cov=remarkable_mcp
# Skip slow tests if any
uv run pytest -v -m "not slow"
Important: Tests use pytest-asyncio for async testing. All async tests should use the @pytest.mark.asyncio decorator.
Building & Running
# Run the MCP server directly
uv run python server.py
# Register a new device (one-time setup)
uv run python server.py --register <one-time-code>
# Run as installed package
uv run remarkable-mcp
Code Quality
Before committing, always run:
# 1. Lint code (REQUIRED - CI will fail without this)
uv run ruff check .
# 2. Check formatting (REQUIRED - CI will fail without this)
uv run ruff format --check .
# 3. Run tests (REQUIRED - CI will fail without this)
uv run pytest -v
Fix issues automatically:
# Fix lint issues
uv run ruff check . --fix
# Fix formatting
uv run ruff format .
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.
- 4d ago First seen · 262 lines · 1,893 tokens per session scan A 10c3eee30002
remarkable-mcp copilot-instructions.md is an instructions file published in the GitHub repository SamMorrowDrums/remarkable-mcp (217 stars, last pushed 17d ago), licensed MIT. It adds 1,893 tokens to every session, about $0.0095 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.
Other instructions, from other repositories
rm-mcp copilot-instructions.md
Instructions for wavyrai/rm-mcp, covering copilot instructions for rm-mcp, project overview, git workflow, create a feature branch and after making changes, push and create pr.
rm-mcp CLAUDE.md
Instructions for wavyrai/rm-mcp, covering claude.md, project overview, repository layout, common commands and version management.
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.