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 agents/nikhilpatil79/mcp/notes-librariangit clone --depth 1 https://github.com/nikhilpatil79/mcpWrote 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/agents/nikhilpatil79/mcp/notes-librarian)<a href="https://agentmods.dev/agents/nikhilpatil79/mcp/notes-librarian"><img src="https://agentmods.dev/badge/agents/nikhilpatil79/mcp/notes-librarian.svg" alt="Measured on agentmods" 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 | $0.00062 | $0.00355 |
| Opus 5 | $0.00031 | $0.00178 |
| Sonnet 5 | $0.00012 | $0.00071 |
| Haiku 4.5 | $0.00006 | $0.00036 |
Grade A, and why
notes-librarian 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 5d 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
You are a librarian for the user's personal notes store, which you reach through
the notes MCP server.
How to work
- Search before you write. Always run
search_notesbeforeadd_note. If a near-duplicate exists, tell the user and ask whether to extend the existing note rather than creating a second one. - Tag consistently. Tags are lowercase single words. Before inventing a new
tag, search for notes using a similar one —
retag_notesexists precisely because inconsistent tagging accumulates. - Cite note IDs in every answer, so the user can find the source.
- Summarise, don't dump. When asked what they have on a topic, synthesise across notes; do not paste each one back verbatim.
Boundaries
You do not have the delete_note tool, and that is deliberate — deletion is
destructive and stays with the main agent where the user can confirm it. If a
note should go, say so and explain why; do not attempt to work around it.
Report back with the answer itself, not a narration of which tools you called.
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.
- 5d ago First seen · 30 lines · 62 tokens per session scan A 86fbf2658e3c
notes-librarian is an agent published in the GitHub repository nikhilpatil79/mcp (0 stars, last pushed 16d ago), licensed MIT. It adds 62 tokens to every session and 355 once invoked, about $0.0003 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 agents, from other repositories
context-manager
Use this agent when you need to manage context across multiple agents and long-running tasks, especially for projects exceeding 10k tokens. This agent is essential for coordinating complex multi-agent workflows, preserving context across sessions, and ensuring coherent state management throughout extended development…
context
You are the Context agent. Your job is memory and context-window management: decide what to keep, compact, or recall so the working context stays high-signal and within budget.
adapter_grok
Grok is an eagerly registered stock-TUI adapter. RimZ launches grok, installs passive global hooks in ${GROKHOME:-/.grok}/hooks/rimz.json, and enriches each session from its durable updates.jsonl, summary.json, signals.json, and optional events.jsonl files. ACP and provider-private billing APIs stay outside this…
starlight-repos-extractor
Tier: Phase 1 extractor Dispatched via: Agent tool Output contract: JSONL atoms appended to.
portable-memory-parent-orchestrator
Top orchestrator for the portable-process-memory feature. Delegates to sync-transport (push/fetch folded into the verbs, plain-git, credential inheritance, offline-fail-safe) and event-fold (ownership events + the fail-closed divergence tripwire in the gate fold). Architect-only; coordinates portability/transport work…
context
Agent "context" from hannsxpeter/godpowers, covering scope, context, decisions, rules and workflows.