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/treylom/knowledge-manager/zettelkasten-notenpx skills add treylom/knowledge-manager --skill zettelkasten-notegit clone --depth 1 https://github.com/treylom/knowledge-managerWrote 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/treylom/knowledge-manager/zettelkasten-note)<a href="https://agentmods.dev/skills/treylom/knowledge-manager/zettelkasten-note"><img src="https://agentmods.dev/badge/skills/treylom/knowledge-manager/zettelkasten-note.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.00016 | $0.00408 |
| Opus 5 | $0.00008 | $0.00204 |
| Sonnet 5 | $0.00003 | $0.00082 |
| Haiku 4.5 | $0.00002 | $0.00041 |
Grade A, and why
zettelkasten-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 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.
What it actually says
Zettelkasten Note Creation
Create atomic, self-contained, interconnected notes
Core Principles
1. Atomicity
- One idea per note
- If you can split it, split it
- Note should be about ONE concept
2. Self-Contained
- Note must be understandable without context
- Include enough background information
- Reader shouldn't need to read other notes first
3. Connectivity
- Link to related notes with
[[wikilinks]] - Explain the relationship in the link
- Build a knowledge network
Note Structure
---
tags: [{domain}, {topic}, {type}]
created: {YYYY-MM-DD}
source: {url_or_reference}
type: zettelkasten
---
# {Concept Name}
> {One-sentence definition or summary}
## Explanation
{2-3 paragraphs explaining the concept}
{Include examples if helpful}
## Key Characteristics
- Characteristic 1
- Characteristic 2
- Characteristic 3
## Connections
- [[Related Concept A]] - {how they relate}
- [[Related Concept B]] - {how they relate}
- [[Contrasting Concept]] - {how they differ}
## Examples
{Concrete examples or applications}
## Source
- {Original source with link}
Folder Organization
Vault/
├── Zettelkasten/
│ ├── AI-Research/
│ ├── Programming/
│ └── Productivity/
├── Research/
│ └── Papers/
├── Threads/
└── Inbox/
Naming Convention
{Topic} - {Specific Concept}.md
Examples:
MCP - Protocol Overview.mdZettelkasten - Atomicity Principle.mdClaude Code - Hooks System.md
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 · 97 lines · 16 tokens per session scan A 11e32c5b06c6
zettelkasten-note is a skill published in the GitHub repository treylom/knowledge-manager (230 stars, last pushed today), licensed MIT. It adds 16 tokens to every session and 408 once invoked, about $0.0001 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-09-01.
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…