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/jaansokk/cursor_tools/noteplannpx skills add jaansokk/cursor_tools --skill noteplangit clone --depth 1 https://github.com/jaansokk/cursor_toolsWhat 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.00105 | $0.01373 |
| Opus 5 | $0.00053 | $0.00687 |
| Sonnet 5 | $0.00021 | $0.00275 |
| Haiku 4.5 | $0.00011 | $0.00137 |
Grade A, and why
noteplan 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.
How it starts
The opening of the file, as written. The whole thing — 110 lines — stays where its author put it; the contents beside it link to each section on GitHub.
NotePlan — Filesystem Access
Read, search, create, and edit NotePlan 3 notes directly through the local filesystem. This is faster than the MCP server and supports bulk operations.
Root path
~/Library/Containers/co.noteplan.NotePlan3/Data/Library/Application Support/co.noteplan.NotePlan3/
Always reference this as NP_ROOT in commands. Use the full expanded path with $HOME — do NOT use ~ inside quoted strings in shell commands.
Directory structure
| Path | Contents | Naming |
|---|---|---|
Calendar/ |
Daily notes | YYYYMMDD.txt (e.g. 20260317.txt) |
Calendar/ |
Weekly notes | YYYY-WNN.txt (e.g. 2025-W47.txt) |
Notes/ |
Project & reference notes | Organized in folders |
Notes folder hierarchy
Notes/
├── 1 Projects/ # Active projects with subfolders
├── 2 Areas/ # Ongoing areas of responsibility
├── 3 Resources/ # Reference material
├── 5 Meetings/ # Meeting notes
├── @Archive/ # Archived notes
├── @Templates/ # Note templates
└── @Trash/ # Deleted notes
File format
NotePlan files are plain-text markdown (.txt extension) with these conventions:
- First line:
# Titleheading (for project notes) or date-based content start (for daily notes) - Tasks (
*):* task(open),* [x] task(done),* [-] task(cancelled). Tasks are tracked — uncompleted tasks become overdue and show up in reviews. Use sparingly, only for items with a real commitment to complete. - Checklist items (
+):+ item(open),+ [x] item(done). Checklists are not tracked — they won't appear as overdue. Use+as the default for notes, ideas, bullets, and anything that doesn't need deadline tracking. - Indented sub-items: tabs for nesting under tasks or checklist items
- Sections:
## Headingor---dividers - Scheduled items:
>YYYY-MM-DDmoves/schedules a task to a date - Links:
[[Note Title]]for internal wiki-links - Tags:
#tagand@mention - Time blocks:
* Task HH:MM-HH:MMor* Task HH:MMfor calendar-like entries
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 · 110 lines · 105 tokens per session scan A 51c825418b72
noteplan is a skill published in the GitHub repository jaansokk/cursor_tools (1 stars, last pushed 5mo ago), licensed MIT. It adds 105 tokens to every session and 1,373 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-31.
Other skills, from other repositories
ab-testing-framework
Design, run, and analyze A/B tests (controlled experiments) using Ronny Kohavi's methodology and Gibson Biddle's DHM trade-off analysis. Use when the user needs to plan an experiment, choose metrics (OEC), evaluate statistical significance, assess sample size requirements, avoid common experimentation pitfalls, or…
continuous-discovery
Guide teams through building sustainable customer interview habits and discovery practices. Use when setting up weekly customer interviews, preparing interview guides, coaching story-based interviewing technique, synthesizing user research findings, planning assumption tests, or helping teams that say they don't have…
prd-writer
Guide users through writing Product Requirements Documents (PRDs) and decomposing them into executable technical tasks. Use when creating a PRD, product spec, product one-pager, feature brief, PRP, or when breaking requirements into tasks with estimates, sprint planning, or technical decomposition.
product-led-growth-playbook
Evaluate growth strategy, growth team structure, and go-to-market motions using Elena Verna's PLG frameworks. Use when the user asks about product-led growth, PLG, growth team hiring, self-serve vs sales-led motions, product-led sales, PQA/PQL models, growth loops, when to hire a head of growth, earned vs rented…
ai-evals-builder
Build AI evals using the Husain-Shankar framework (error analysis, open/axial coding, LLM-as-judge). Use when a user needs to create, improve, or debug evals for an AI product — including defining failure modes, building LLM judges, or setting up production monitoring for an LLM application.
dhm-strategy-framework
Evaluate and strengthen product strategy using Gibson Biddle's DHM framework (Delight, Hard-to-copy, Margin-enhancing). Use when the user asks about product strategy, competitive advantage, feature prioritization trade-offs, or wants to stress-test whether a product idea is strategically sound.