joplin-server-vector-memory: Instructions file for Gemini CLI

GEMINI.md

joplin-server-vector-memory GEMINI.md is an instructions file for Gemini CLI from adamoutler/joplin-server-vector-memory. It costs 489 tokens per session, scanned A, original, ISC.

A set of Gemini CLI instructions for working on a Joplin Server vector-memory MCP project. It describes how to explore code, refactor it, test it, and follow its architecture.

In plain words
What is it for?
Use it when discovering code, improving code quality, running tests, or making architectural changes in this project.
Why use it?
It gives the coding agent project-specific guidance instead of leaving it to guess how the repository is organised or changed.

Instructions file for Gemini CLI

Written for Gemini CLI: the file is GEMINI.md. Also seen: mentions Gemini CLI.

This is adamoutler/joplin-server-vector-memory's own configuration. It tells Gemini CLI how to work on joplin-server-vector-memory itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything joplin-server-vector-memory configures →

Reuse

Borrowing it

Nothing to install: this file belongs to adamoutler/joplin-server-vector-memory. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/adamoutler/joplin-server-vector-memory/main/GEMINI.md
Clone the repo
git clone --depth 1 https://github.com/adamoutler/joplin-server-vector-memory

Made for: Gemini CLI.

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.

agentmods badge for joplin-server-vector-memory GEMINI.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/adamoutler/joplin-server-vector-memory/gemini-md/github.svg)](https://agentmods.dev/instructions/adamoutler/joplin-server-vector-memory/gemini-md)
Your own site
<a href="https://agentmods.dev/instructions/adamoutler/joplin-server-vector-memory/gemini-md"><img src="https://agentmods.dev/badge/instructions/adamoutler/joplin-server-vector-memory/gemini-md/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for joplin-server-vector-memory GEMINI.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/adamoutler/joplin-server-vector-memory/gemini-md"><img src="https://agentmods.dev/badge/instructions/adamoutler/joplin-server-vector-memory/gemini-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 489 This file is loaded in full into every session.
When invoked 489 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00489 $0.00489
Opus 5.5 $0.00196 $0.00196
Sonnet 5.5 $0.00098 $0.00098
Haiku 4.5 $0.00049 $0.00049

Measured 1mo ago against content hash d6217eaf2455, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

joplin-server-vector-memory GEMINI.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 1mo 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.

GEMINI.md · 28 lines

How it starts

The opening of the file, as written. The whole thing — 28 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Joplin Server Vector Memory MCP - Gemini Methodology

This document outlines the methodology and guidelines for future AI incarnations (specifically Gemini CLI agents) working on this codebase.

1. Code Discovery & Context Gathering

  • Use Dedicated Tools: Always use glob, list_directory, and grep_search rather than shelling out to ls, find, or grep. This reduces context bloat and ensures fast, targeted discovery.
  • Read Documentation First: Before making any architectural changes, read the 1-GEMINI.md files located in each major directory (/client, /server, /client/src, etc.). They define the boundaries, dependencies, and responsibilities of each module.

2. Refactoring & Code Quality

  • Legibility is Paramount: Prioritize human readability. Use descriptive variable names, extract complex logic into smaller, well-named functions, and ensure consistent formatting.
  • Docstrings & JSDoc: Any new functions or major changes to existing ones should be documented using standard Python docstrings or JSDoc comments to describe parameters, return types, and potential exceptions.
  • Behavior Preservation: Refactoring should never alter external API contracts or break the E2EE encryption/decryption flows.

3. Execution & Testing

  • Validation: Never assume a change works just by looking at it. Always run the test suites before claiming success.
    • For the Node.js client: cd client && npm ci && npm test
    • For the Python server: Ensure the venv is active, install requirements, and run pytest.
  • Iterative Commits: Commit logical chunks of work with clear, descriptive commit messages.

4. Architectural Rules

  • No Passwords on Disk: Remember that joplinPassword and joplinMasterPassword are strictly ephemeral. Never write them to config.json.
  • Vector DB Resilience: The sqlite-vec database is treated as ephemeral. If corrupted, it should be wiped and rebuilt from the source notes.
  • Zero-Trust E2EE: Do not expose decrypted note contents outside the local host environment except via the authenticated MCP interface.

Read the full file on GitHub · 28 lines

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. 1mo ago First seen · 28 lines · 489 tokens per session scan A d6217eaf2455

Subscribe to this mod's changes

joplin-server-vector-memory GEMINI.md is an instructions file published in the GitHub repository adamoutler/joplin-server-vector-memory (4 stars, last pushed 5d ago), licensed ISC. It adds 489 tokens to every session, about $0.0020 per session on Opus 5.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.

Related

Other instructions, from other repositories

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).

microsoft/vscode · 9,715 tokens

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.

vercel/next.js · 7,786 tokens

vscode oss-third-party-notices.instructions.md

Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).

microsoft/vscode · 5,262 tokens

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.

langchain-ai/langchain · 4,680 tokens

vscode copilot-instructions.md

Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).

microsoft/vscode · 2,731 tokens

deno copilot-instructions.md

Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.

denoland/deno · 3,077 tokens