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/lukaisailovic/remarkable-mcp/agents-mdgit clone --depth 1 https://github.com/lukaisailovic/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/lukaisailovic/remarkable-mcp/agents-md)<a href="https://agentmods.dev/instructions/lukaisailovic/remarkable-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/lukaisailovic/remarkable-mcp/agents-md.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.00699 | $0.00699 |
| Opus 5 | $0.00349 | $0.00349 |
| Sonnet 5 | $0.00140 | $0.00140 |
| Haiku 4.5 | $0.00070 | $0.00070 |
Grade A, and why
remarkable-mcp AGENTS.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 — 35 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent notes
pnpm, Node 22+, TypeScript ESM (NodeNext). Imports end in .js. No enums, no constructor parameter properties (erasableSyntaxOnly).
One MCP tool: remarkable_execute. Sandbox global is rme, not codemode. Do not register a dozen remarkable_* tools.
Storage: SSH into xochitl (default) or rmfakecloud sync v3 (RMFAKECLOUD_URL + device token / --pair). No official reMarkable Cloud (my.remarkable.com, REMARKABLE_TOKEN), no USB-web (http://10.11.99.1 as an HTTP API). Tablet FS path for SSH is /home/root/.local/share/remarkable/xochitl.
Do not import from @cloudflare/codemode (main entry needs cloudflare:workers). HTTP uses @modelcontextprotocol/sdk Streamable HTTP.
Layout
| Path | Role |
|---|---|
src/api.ts |
Typed tablet API (createApi) |
src/fs.ts |
MemoryFs / LocalFs / SshFs + apply() |
src/cloud.ts |
rmfakecloud sync v3 (CloudFs) |
src/xochitl.ts |
.metadata / .content JSON |
src/rm.ts |
.rm strokes, SVG/PNG |
src/mermaid.ts |
Mermaid → SVG (beautiful-mermaid) → ink |
src/pdf.ts |
PDF/EPUB text (unpdf, jszip) |
src/server.ts |
MCP wrap → remarkable_execute |
src/http.ts |
Streamable HTTP /mcp |
src/index.ts |
stdio default; --http / MCP_HTTP=1 |
Conventions that bite
- Resolve notebooks by UUID, unique name, or
/Folder/Name. Pages are 1-based. Ink points are 0–1 from top-left.writeTextis native Type Folio and appends. remove= trash (parent: "trash"), not unlink. Writesapply()once per tool call (SSH: restart xochitl; cloud: PUT blobs +/sync/v3/root).- Tests:
REMARKABLE_FAKE=1/MemoryFs. Never need a live tablet.pnpm test(vitest). Optionalpnpm test:e2e(Docker rmfakecloud). Lint/fmt/build:oxlint,oxfmt,rolldown. - Local
.mcp.jsonrunssrc/dev-stdio.ts: savingsrc/*.tsrestarts the MCP child; Grok stays up./mcpsdisable+enable also respawns.rin/mcpsonly refreshes the list. - Skill:
skills/remarkable-mcp/SKILL.md—namemust match the directory.
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 · 35 lines · 699 tokens per session scan A 657c81db884c
remarkable-mcp AGENTS.md is an instructions file published in the GitHub repository lukaisailovic/remarkable-mcp (0 stars, last pushed 16d ago), licensed MIT. It adds 699 tokens to every session, about $0.0035 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).
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.
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).