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 jamesfishwick/slipbox-mcp --skill slipbox-analyze-notegit clone --depth 1 https://github.com/jamesfishwick/slipbox-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/skills/jamesfishwick/slipbox-mcp/slipbox-analyze-note)<a href="https://agentmods.dev/skills/jamesfishwick/slipbox-mcp/slipbox-analyze-note"><img src="https://agentmods.dev/badge/skills/jamesfishwick/slipbox-mcp/slipbox-analyze-note/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/jamesfishwick/slipbox-mcp/slipbox-analyze-note"><img src="https://agentmods.dev/badge/skills/jamesfishwick/slipbox-mcp/slipbox-analyze-note.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.00091 | $0.00807 |
| Opus 5.5 | $0.00036 | $0.00323 |
| Sonnet 5.5 | $0.00018 | $0.00161 |
| Haiku 4.5 | $0.00009 | $0.00081 |
Grade A, and why
slipbox-analyze-note 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.
How it starts
The opening of the file, as written. The whole thing — 96 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Analyze Note
Analyze this note for integration into my Zettelkasten. Use the slipbox tools to ground your suggestions in my actual knowledge base.
1. Atomicity Check
Does the note contain exactly one idea? If multiple concepts are present:
- List each distinct idea that should be its own note
- Identify the primary idea vs. supporting details
- Search first to flag any that duplicate existing notes
2. Connectivity Analysis
Do this before suggesting connections:
- Extract 2-3 key terms from the note
- Run
slipbox_search_notesfor each term to find related existing notes - Run
slipbox_find_similar_notesif this is an existing note ID - Check
slipbox_find_central_notesto see if this relates to a knowledge hub
Then report:
- Specific existing notes this should link to (with IDs and titles)
- Recommended link types for each connection:
extends— builds on the target noterefines— clarifies or improves the targetcontradicts— presents opposing viewquestions— raises doubts about the targetsupports— provides evidence for the targetrelated— loose thematic connection
3. Clarity Enhancement
Rewrite the note to:
- Express one idea clearly and completely
- Stand alone without external context
- Use terminology consistent with existing notes (check related notes for conventions)
- Stay within 3-7 paragraphs
Provide the rewritten version in a code block for easy copying.
4. Metadata Suggestions
Tags: Run slipbox_get_all_tags first. Suggest 3-5 tags, preferring existing tags over new ones. If proposing a new tag, justify why existing tags don't fit.
Title: Propose a clear, searchable title that expresses the core idea.
Note type:
fleeting— raw capture, needs processingliterature— extracted from a source. REQUIRES at least one entry inreferences. Usefleetingif you don't have the citation yet.permanent— refined idea in user's own wordsstructure— organizes 7-15 related notes on a topichub— entry point to a major knowledge domain
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 · 96 lines · 91 tokens per session scan A 1394eb81357e
slipbox-analyze-note is a skill published in the GitHub repository jamesfishwick/slipbox-mcp (2 stars, last pushed 1mo ago), licensed MIT. It adds 91 tokens to every session and 807 once invoked, about $0.0004 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
knowledge-ingest
Ingest documents, articles, conversations, or supplied text into Knowledge with retained originals, sourced claims, entity updates, timelines, and cross-links; also learn durable lessons from a set of conversations, transcripts, or past sessions (/learn), including the Learn from conversations and Learn from Memory…
mem0-oss-to-platform
Plan, then execute, a migration of a project from the mem0 open-source / self-hosted SDK (local Memory class) to the mem0 Platform / hosted SDK (MemoryClient). TRIGGER when: the developer wants to move, switch, or migrate mem0 off OSS/self-hosted to the hosted API, e.g. "migrate my mem0 setup to the platform", "switch…
forget
Remove a personal fact, preference, relationship detail, topic, or prior event from Muse's active memory and stop existing copies or automations from bringing it back. Use for explicit requests such as 'forget that', 'don't remember this about me', or 'remove that from your memory'. Do not use when 'forget it' merely…
Cortex
LifeOS memory, prior-session recall, and learning capture. USE WHEN capture this learning, document this learning, what did we learn recently, recent learnings, cortex, knowledge, knowledge base, search knowledge, what do we know about, archive, harvest, knowledge status, develop note, add to knowledge, add a people…
memory
Use when the user asks to remember, recall, forget, update, search, or inspect durable OpenSquilla memory, including profile facts in USER.md and long-term notes in MEMORY.md or memory//.md.
ha-data-stores
Map of Hope Agent's local data stores and safe read-only query workflow. Use when the user asks where Hope Agent stores data, wants to inspect sessions/messages/memory/logs/background jobs/knowledge indexes/settings, asks the model to query local app data, or debugging requires checking persisted state. Trigger…