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 mikonos/zettelkasten-agent-skills --skill literature-notegit clone --depth 1 https://github.com/mikonos/zettelkasten-agent-skillsWrote 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/mikonos/zettelkasten-agent-skills/literature-note)<a href="https://agentmods.dev/skills/mikonos/zettelkasten-agent-skills/literature-note"><img src="https://agentmods.dev/badge/skills/mikonos/zettelkasten-agent-skills/literature-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/mikonos/zettelkasten-agent-skills/literature-note"><img src="https://agentmods.dev/badge/skills/mikonos/zettelkasten-agent-skills/literature-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.00000 | $0.00792 |
| Opus 5 | $0.00000 | $0.00396 |
| Sonnet 5 | $0.00000 | $0.00158 |
| Haiku 4.5 | $0.00000 | $0.00079 |
Grade A, and why
literature-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 11d 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 — 97 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Literature Note (high-output)
Role
Combine:
- Luhmann (links first)
- Feynman (can-you-teach test)
- First principles (mechanisms, constraints, leverage)
Output contract (hard constraints)
- Naming / ID: use
YYYYMMDD_HH_Topicconsistently (file name == ID). - Keep concrete details: names, numbers, platforms, specific actions, timelines.
- How > What: every framework/tool must include steps + template + checklist + pitfalls + evaluation.
- Links: end with ≥2 meaningful
[[bidirectional links]](state the link type). - Unknowns: mark as
TBDand list what to clarify. - Diagrams: use PlantUML when a diagram is needed.
Workflow
Step 0: TODO first
Draft a task checklist (≥6 items), then execute, then report completion + QA.
Step 1: Define inputs (boundary conditions)
- Material type + source (author/link/date; otherwise
TBD) - Your use case (decision / execution / skill building / writing / review)
- Output granularity (toolbox vs full framework)
Step 2: Four-pass reading
- Frame: structure + main claim + argument path
- Tooling: extract all tools/templates/checklists (keep details)
- Network: propose ≥5 link candidates, keep the best ≥2
- Completeness: missing tools / boundaries / counterexamples / prerequisites
Step 3: Atomize when needed
If there are ≥3 independent concepts/tools, split into multiple notes + create an index note.
Step 4: Tool extraction (6 required fields)
For each tool:
- purpose
- inputs / prerequisites
- steps (doable)
- template (copy-paste)
- acceptance checklist
- pitfalls / failure modes + prevention
Output template (single file)
# YYYYMMDD_HH_Topic
## 🆔 ID
ID: [[YYYYMMDD_HH_Topic]]
## Source
- Type:
- Author/org:
- Link/path:
- Date/version:
- Use case:
- Importance: L1/L2/L3 (why)
## One-sentence summary (Feynman)
> What problem does it solve, by what mechanism, and how to apply it?
## Frame
- Main claim:
- Argument path: A → B → C
- Key conclusions (3–7):
## Tool library (high signal)
| Tool | Purpose | Inputs | Steps | Template | Checklist | Pitfalls | Evaluation |
|---|---|---|---|---|---|---|---|
## Next experiments
- [ ] Smallest actionable experiment this week (owner/date can be TBD)
## Links (≥2, explain why)
- [[Note A]]: supplement/contrast/apply/analogy/counterexample — why
- [[Note B]]: ...
## QA (results only)
- Extracted: concepts X / tools Y / cases Z
- Structure: Frame clear / How executable / Why includes mechanism + boundaries
- Links: N links with reasons
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.
- 11d ago First seen · 97 lines · 0 tokens per session scan A 4f18916d2167
literature-note is a skill published in the GitHub repository mikonos/zettelkasten-agent-skills (2 stars, last pushed 7mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 792 tokens. 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…