np-programming-general

A set of programming rules for NotePlan plugins. It defines constraints such as using static imports and explains NotePlan-specific task priority markers and coding conventions.

In plain words
What is it for?
Use it when writing or reviewing NotePlan plugin code, choosing imports, handling task priorities, checking API types, and following the project’s Flow, formatting, and style rules.
Why use it?
It prevents implementation choices that the project’s build system or NotePlan’s API does not support. It also keeps user-facing priority handling consistent with NotePlan’s actual symbols.

Cursor rule for Cursor

Install

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.

agentmods
npx agentmods add rules/noteplan/plugins/np-programming-general
Clone the repo
git clone --depth 1 https://github.com/NotePlan/plugins

Made for: Cursor.

Per session 948 This file is loaded in full into every session.
When invoked 948 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
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 $0.00948 $0.00948
Opus 5 $0.00474 $0.00474
Sonnet 5 $0.00190 $0.00190
Haiku 4.5 $0.00095 $0.00095

Measured 2d ago against content hash 703f981484d3, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

np-programming-general 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 2d 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.

.cursor/rules/np-programming-general.mdc · 61 lines

How it starts

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

Critical Rules

CRITICAL: Never use dynamic imports. Rollup will not process them correctly. Always use static imports at the top of files.

NotePlan domain facts

  • NotePlan's supported task priority markers are exactly !, !!, !!!, and >>. The corresponding paragraph.priority values are 1, 2, 3, and 4. !!!! (four exclamation marks) is NOT a supported priority marker.
  • "priority marker" or just "Marker" is user-facing language. Users think in terms of the symbols (>>, !!!, !!, !), not the underlying numeric .priority values. Use the symbols in settings/labels/descriptions, but key code logic off .priority when possible.
  • Prefer @flow-typed/Noteplan.js over the public website when looking up NotePlan plugin APIs (Calendar, CalendarItem, Editor, DataStore, etc.). That file is usually more detailed and closer to what Eduard ships. Offer to sync missing notes into it when you learn them from gists/changelogs, but ensure developer specifically checks and approves the change.

Code Style Guidelines

  • Use Flow for static typing
  • No semicolons (enforced by ESLint/Prettier)
  • Single quotes for strings
  • Max line length: 180 characters
  • Keep logDebug, logInfo, logWarn, logError, and clo() calls on a single line when possible; do not wrap them across multiple lines to satisfy the max line length rule
  • Use template literals instead of string concatenation
  • Use ES6+ features (const/let, arrow functions)
  • Use async/await and handle promises properly (no floating promises)
  • Follow existing naming patterns in the codebase
  • Proper error handling with try/catch blocks
  • Follow import order: external libs -> internal libs -> local files. Within that put in alphabetical order of source filename.
  • Keep code DRY and modular with clear function responsibilities
  • Add JSDoc comments for all functions
  • Always research the helpers/ folder before writing new code
  • Prefer writing explicit functions over constant declarations
  • When moving code, keep existing comments and commented-out code
  • Please provide Flow types (as appropriate) and JSDOC with all responses.
  • If you are rewriting a full file, make sure to include all import statements also.
  • Do not remove any console.logs or comments (or clo, logDebug, logWarn, logInfo, logError statements).

Read the full file on GitHub · 61 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. 2d ago First seen · 61 lines · 948 tokens per session scan A 703f981484d3

Subscribe to this mod's changes

np-programming-general is a cursor rule published in the GitHub repository NotePlan/plugins (204 stars, last pushed 2d ago), licensed MIT. It adds 948 tokens to every session, about $0.0047 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.