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 skills/noteplan/plugins/nplognpx skills add NotePlan/plugins --skill nploggit clone --depth 1 https://github.com/NotePlan/pluginsWhat 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.00109 | $0.01538 |
| Opus 5 | $0.00055 | $0.00769 |
| Sonnet 5 | $0.00022 | $0.00308 |
| Haiku 4.5 | $0.00011 | $0.00154 |
Grade A, and why
nplog 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 3d 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 — 117 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Reading the NotePlan plugin log
scripts/nplog/nplog (in this repo) parses NotePlan's log into structured records.
Run it as node scripts/nplog/nplog from the repo root, or just nplog if
scripts/nplog/install.sh has been run.
Always use --json for programmatic reading. The default mode is a full-screen
interactive viewer for humans and will hang a non-TTY caller.
The core loop: "what happened when I did X?"
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
An x-callback returns immediately while the plugin keeps running — a Dashboard refresh ping-pongs asynchronously for anywhere from 2 to 30 seconds. Do not guess a duration:
--followstreams entries as they arrive.--wait-idle 5stops after five seconds of silence. A run still in flight writes something within five seconds, so that much quiet means it finished.--timeout(default 90s) is the hard cap.
The log flushes in batches. Measured: the file sat untouched for 24s after an action,
then gained 80 lines at once. So never conclude "the action logged nothing" from an empty
result — check the summary's sawOutput and timedOut fields, which exist precisely to
tell that apart from "I looked too early". Do not lower --timeout below ~30s.
Exit code 1 means at least one emitted entry was an ERROR — check it before reading anything, it is the cheapest possible signal.
Recipes
# only the most recent plugin invocation
node scripts/nplog/nplog --json --last-run
# the last 10 minutes (also accepts 30s / 2h / a bare number = minutes,
# or a local wall-clock time like 19:36 or "2026-07-29 19:36")
node scripts/nplog/nplog --since 10m --json
# problems only
node scripts/nplog/nplog --since 10m --json --min-level warn
# find a diagnostic line and see the 10 entries that followed it
node scripts/nplog/nplog --json --mode 10 '\[DIAG\]'
# keep the output small (default 500; truncation is always reported, never silent)
node scripts/nplog/nplog --since 1h --json --max-entries 50
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.
- 3d ago First seen · 117 lines · 109 tokens per session scan A 7f5e34904e1a
nplog is a skill published in the GitHub repository NotePlan/plugins (204 stars, last pushed 3d ago), licensed MIT. It adds 109 tokens to every session and 1,538 once invoked, about $0.0005 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.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…