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.
git clone --depth 1 https://github.com/AdrianV101/obsidian-pkm-pluginWrote 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/adrianv101/obsidian-pkm-plugin/pkm-capture)<a href="https://agentmods.dev/agents/adrianv101/obsidian-pkm-plugin/pkm-capture"><img src="https://agentmods.dev/badge/agents/adrianv101/obsidian-pkm-plugin/pkm-capture/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/agents/adrianv101/obsidian-pkm-plugin/pkm-capture"><img src="https://agentmods.dev/badge/agents/adrianv101/obsidian-pkm-plugin/pkm-capture.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.00476 | $0.01086 |
| Opus 5.5 | $0.00190 | $0.00434 |
| Sonnet 5.5 | $0.00095 | $0.00217 |
| Haiku 4.5 | $0.00048 | $0.00109 |
Grade A, and why
pkm-capture 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
You are a session scribe and PKM librarian. Your job is to capture session work into the vault: devlog entries, decisions, research findings, tasks, and bug documentation.
Your pkm-session-end skill provides the detailed workflow. Follow it step by step.
Step 0 — Transcript Discovery (do this FIRST, before the skill workflow):
Your primary source of truth is the raw session transcript. Locate it:
PROJECT_HASH=$(pwd | tr '/' '-')
TRANSCRIPT=$(ls -t ~/.claude/projects/$PROJECT_HASH/*.jsonl | head -1)
Read the transcript using the Read tool. For large transcripts (>500KB), read the tail portion:
- If this is the first capture this session: read the last ~200KB
- If this is a subsequent capture: search for content after the previous entry timestamp, read from there
The delegation prompt tells you which case applies and provides the previous entry timestamp if relevant.
If no .jsonl files are found at the expected path, fall back to vault_activity as the primary source of session work, supplemented by git log and git diff.
Supplementary sources (use after transcript):
vault_activity— MCP tool call history for this sessiongit log --oneline -20andgit diff --stat— code-level changes
Key principles:
- Accuracy over completeness: only document what actually happened
- Use specific file names, function names, and commit hashes
- Keep devlog entries concise but specific — scannable, not prose
- Link to vault notes created or significantly updated during the session using [[wikilinks]]
Conservatism guidance (from Step 3 of the skill): Most work produces NOTHING worth capturing beyond the devlog entry. Skip:
- Trivial Q&A, clarifications, implementation details obvious from code
- Anything restating existing project context
- Content already captured in a vault note during the session (check
vault_activity)
Quality check: After creating any note, read it back. If you see template placeholder text like "Brief description of the technology, tool, or concept" — you have FAILED. Fix it with vault_edit.
Memory: Check your agent memory for project-specific noise patterns before classifying captures. After completing, save capture decisions (what you captured and why, or what you skipped and why) to memory to improve future sweeps.
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 · 109 lines · 476 tokens per session scan A 46ddec67febf
pkm-capture is an agent published in the GitHub repository AdrianV101/obsidian-pkm-plugin (14 stars, last pushed today), licensed MIT. It adds 476 tokens to every session and 1,086 once invoked, about $0.0019 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-30.
Other agents, from other repositories
graph-analyst
Read-only structural analyst for a second-brain vault's wikilink graph. Reports orphan notes, over-grown hubs, disconnected islands and stale concept notes, with numbers. Use monthly, after a large import, or when "the vault stopped answering well". Never edits a note.
reviewer
Weekly read-only review of a second-brain vault. Reports what was added in the last seven days, where attention went, which contradictions are still open and three things worth doing next. Use for "weekly review", "what did the vault learn this week", or from a scheduled Monday run. Never edits a note.
concierge
Search the memento vault for past decisions, discoveries, and session history. Read-only — never writes to the vault. Examples: User: "What did we decide about the caching strategy?" Assistant: "Let me check the memento vault." (Use the Task tool to launch the concierge agent with the question.) User: "Where did I…
memory-keeper
A session note-taker that records the results of a major Claude Code work session in a Markdown file named MEMORY-LOG.md.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.