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 skills add Proxy2021/Enso --skill note_keepergit clone --depth 1 https://github.com/Proxy2021/EnsoWrote 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.
[](https://agentmods.dev/skills/proxy2021/enso/note_keeper)<a href="https://agentmods.dev/skills/proxy2021/enso/note_keeper"><img src="https://agentmods.dev/badge/skills/proxy2021/enso/note_keeper/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.
<a href="https://agentmods.dev/skills/proxy2021/enso/note_keeper"><img src="https://agentmods.dev/badge/skills/proxy2021/enso/note_keeper.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.1 | $0.00012 | $0.00208 |
| Opus 5.5 | $0.00005 | $0.00083 |
| Sonnet 5.5 | $0.00002 | $0.00042 |
| Haiku 4.5 | $0.00001 | $0.00021 |
Grade A, and why
note_keeper 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.
What it actually says
Note Keeper
Persistent notes with search, tags, and organization
Available Tools
enso_note_keeper_list_notes (primary)
List all saved notes with title, preview, tags, and timestamps
Parameters:
tag(string): Filter by tag (optional)
enso_note_keeper_save_note
Create or update a note with title, body, and optional tags
Parameters:
id(string): Note ID (omit to create new, provide to update)title(string): Note titlebody(string): Note body contenttags(string): Comma-separated tags
enso_note_keeper_delete_note
Delete a note by ID
Parameters:
id(string): Note ID to delete
enso_note_keeper_search_notes
Full-text search across all notes
Parameters:
query(string): Search query
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.
- 1mo ago First seen · 42 lines · 12 tokens per session scan A b734edf87cc1
note_keeper is a skill published in the GitHub repository Proxy2021/Enso (6 stars, last pushed 5mo ago), licensed MIT. It adds 12 tokens to every session and 208 once invoked, about $0.0000 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.
Other skills, from other repositories
nap
Reclaims context window budget by compressing agent histories, pruning old logs, archiving stale decisions, and cleaning orphaned inbox files.
memory-grounding
Recall past conversations, feelings, and diary entries for personal grounding.
remember
Store a persistent memory fact.
recall
Retrieve stored memories.
android-leak-expert
Expert guide for detecting, profiling, and resolving memory leaks in Android apps (Java, Kotlin, Compose, JNI). Use when analyzing memory usage, profiling heap dumps, fixing out-of-memory (OOM) issues, checking Compose lifecycle flow collections, resolving WebView/Handler leaks, or configuring LeakCanary. Triggers…
history-hygiene
Record final outcomes to history.md, not intermediate requests or reversed decisions.