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/rbonitz/remarkable-mcp-http-/copilot-instructionsgit clone --depth 1 https://github.com/rbonitz/remarkable-mcp-http-Wrote 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/rbonitz/remarkable-mcp-http-/copilot-instructions)<a href="https://agentmods.dev/instructions/rbonitz/remarkable-mcp-http-/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/rbonitz/remarkable-mcp-http-/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.01693 | $0.01693 |
| Opus 5 | $0.00847 | $0.00847 |
| Sonnet 5 | $0.00339 | $0.00339 |
| Haiku 4.5 | $0.00169 | $0.00169 |
Grade A, and why
remarkable-mcp-http- 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.
This is a copy
100% identical to remarkable-mcp copilot-instructions.md — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 244 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 FastMCP.
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 test_server.py -v
For specific test patterns:
# Run specific test class
uv run pytest test_server.py -v -k "TestClassName"
# Run with coverage
uv run pytest test_server.py -v --cov=server
# Skip slow tests if any
uv run pytest test_server.py -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 test_server.py -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 · 244 lines · 1,693 tokens per session scan A 617b21cadc4f
remarkable-mcp-http- copilot-instructions.md is an instructions file published in the GitHub repository rbonitz/remarkable-mcp-http- (0 stars, last pushed 2mo ago), licensed MIT. It adds 1,693 tokens to every session, about $0.0085 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to remarkable-mcp copilot-instructions.md, differing in 0 lines, and is treated as a copy.
Other instructions, from other repositories
planning-with-files AGENTS.md
AGENTS.md instructions for OthmanAdi/planning-with-files, covering agents.md — planning-with-files agent reference card, commit rules, release checklist (12 steps), version bump scope and changelog format.
daisyui code_generation_with_git.instructions.md
Instructions for saadeghi/daisyui, covering activation, initial setup, development loop, error handling and session end.
dario CLAUDE.md
Claude Code instructions for askalf/dario, covering dario — notes for claude code (and other llm coding agents), commits and prs, style, scope and when in doubt, ask.
Commit Message
Comprehensive Conventional Commits guidelines for openwebui-extensions.
ai-git-commiter CLAUDE.md
Instructions for zdt1013/ai-git-commiter, covering ai git commiter, 项目结构, 技术栈, 常用命令 and 安装依赖.
orkid CLAUDE.md
Claude Code instructions for tweakoz/orkid, covering orkid — repo-wide agent law and commits.