What is nplog-plugin-logs?

Rules for reading NotePlan plugin logs with the repository's nplog tool. NotePlan is a note-taking app with a plugin system, and its logs contain plugin events and errors.

Use them when debugging a NotePlan plugin, especially when filtering recent runs, inspecting errors, or reading log data in JSON format.

They prevent misleading results caused by searching the raw log file, misreading timestamps, or using an interactive viewer where a script expects structured output.

nplog-plugin-logs — Cursor rule by NotePlan

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/nplog-plugin-logs

Clone the repo

git clone --depth 1 https://github.com/NotePlan/plugins

Made for: Cursor.

Per session 916 This file is loaded in full into every session.

When invoked 916 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.

Model	Per session	Once invoked
Fable 5	$0.00916	$0.00916
Opus 5	$0.00458	$0.00458
Sonnet 5	$0.00183	$0.00183
Haiku 4.5	$0.00092	$0.00092

Measured yesterday against content hash a60850b3e8e7, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

nplog-plugin-logs 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 yesterday.

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/nplog-plugin-logs.mdc · 74 lines

How it starts

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

Reading NotePlan plugin logs

Use nplog (in scripts/nplog/) to read NotePlan's plugin log. Run it as node scripts/nplog/nplog from the repo root, or as nplog after a one-time ./scripts/nplog/install.sh.

Never grep the raw log file

All three obvious greps return empty, and empty reads as "no errors", which is worse than an error:

grep '^JSLog:' matches nothing. Every line has a timestamp before the marker.
grep '| ERROR |' matches nothing. WARN and ERROR use emoji delimiters (🥺 WARN 🥺, ❗️ ERROR ❗️), not pipes. See LOG_LEVEL_STRINGS in helpers/dev.js.
Filtering on the leading timestamp is wrong on about two thirds of lines, by up to hours. That is the flush time, not the event time.

A pretty-printed object also spans a dozen physical lines with only the first carrying the marker, so grepping a field hands back an orphan.

Use --json for programmatic reading

The default mode is a full-screen interactive viewer and will hang a non-TTY caller.

node scripts/nplog/nplog --json --last-run          # the most recent plugin invocation
node scripts/nplog/nplog --since 10m --json         # last 10 minutes (also 30s, 2h, 19:36)
node scripts/nplog/nplog --since 10m --json --min-level warn
node scripts/nplog/nplog --json --mode 10 '\[DIAG\]'  # a match plus the next 10 entries

Output is NDJSON, one object per entry then a summary. Each record carries ts, level (debug/info/warn/error), source (plugin/webview), run (which Executing function invocation it belongs to, so an error can be attributed to the call that caused it), and text (the whole entry, objects intact).

Exit code 1 means at least one emitted entry was an ERROR. Check that before reading anything.

After triggering an action

CURSOR=$(node scripts/nplog/nplog --mark)
open "noteplan://x-callback-url/runPlugin?pluginID=jgclark.Dashboard&command=Show%20Dashboard"
node scripts/nplog/nplog --since "$CURSOR" --follow --wait-idle 5 --json

Read the full file on GitHub · 74 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.

yesterday First seen · 74 lines · 916 tokens per session scan A a60850b3e8e7

Subscribe to this mod's changes

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

Debugging

nplog-plugin-logs

Getting it into your agent

What it costs to keep this loaded

Grade A, and why

Nothing flagged

How it starts

Reading NotePlan plugin logs

Never grep the raw log file

Use --json for programmatic reading

After triggering an action

What this file has done since we first saw it

Other cursor rules, from other repositories

angular-20

dev-standard

typescript

coolify-ai-docs

python_lib

specs