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/takashito/claude-obsidian-chronicleWrote 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/plugins/takashito/claude-obsidian-chronicle/claude-obsidian-chronicle)<a href="https://agentmods.dev/plugins/takashito/claude-obsidian-chronicle/claude-obsidian-chronicle"><img src="https://agentmods.dev/badge/plugins/takashito/claude-obsidian-chronicle/claude-obsidian-chronicle/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/plugins/takashito/claude-obsidian-chronicle/claude-obsidian-chronicle"><img src="https://agentmods.dev/badge/plugins/takashito/claude-obsidian-chronicle/claude-obsidian-chronicle.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
obsidian-chronicle 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 10d 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
{
"$schema": "https://json.schemastore.org/claude-code-plugin-manifest.json",
"name": "obsidian-chronicle",
"displayName": "obsidian chronicle",
"version": "0.2.3",
"description": "Auto-records Claude Code sessions as structured Obsidian notes + Daily Note entries (via the SessionEnd/PreCompact hooks and /done), and ships the obsidian-vault agent — the unified handler for all Obsidian vault work (create, edit, search, organize notes, tasks, canvases, bases). Configure with /obsidian-chronicle:setup.",
"author": {
"name": "takashito",
"url": "https://github.com/takashito"
},
"homepage": "https://github.com/takashito/claude-obsidian-chronicle",
"repository": "https://github.com/takashito/claude-obsidian-chronicle",
"license": "MIT",
"keywords": [
"obsidian",
"session-summary",
"daily-notes",
"journaling",
"knowledge-management",
"hooks",
"claude-code"
],
"hooks": {
"SessionStart": [
{
"hooks": [
{
"type": "command",
"command": "bash \"${CLAUDE_PLUGIN_ROOT}/hooks/session-context.sh\"",
"timeout": 10
}
]
}
],
"SessionEnd": [
{
"hooks": [
{
"type": "command",
"command": "bash \"${CLAUDE_PLUGIN_ROOT}/hooks/session-summary.sh\"",
"timeout": 10
}
]
}
],
"PreCompact": [
{
"hooks": [
{
"type": "command",
"command": "REASON_OVERRIDE=precompact bash \"${CLAUDE_PLUGIN_ROOT}/hooks/session-summary.sh\"",
"timeout": 10
}
]
}
]
}
}
What it installs
The manifest is a name and a version. 2 commands, 1 agent travel with it, and installing the plugin installs all of them — 300 tokens a session between them. Each is measured on its own page, and each can be installed alone.
What ships with it
1 file beside plugin.json in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 10d ago First seen · 59 lines scan A 569a51e0b0c7
obsidian-chronicle is a plugin published in the GitHub repository takashito/claude-obsidian-chronicle (1 stars, last pushed 2mo ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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 plugins, from other repositories
superbrain
Automatic Claude Code -> Obsidian second brain: zero-config session capture, hybrid search, autonomous recall, daily/lessons/preferences.
memex
Collaborative memory for human-AI work — persistent, searchable, interconnected.
obsidian-vfs
Resolve @obs: mentions, and /obs: Skills from your Obsidian vault into Claude.
codex-obsidian-loop
Task-driven Codex + Obsidian loop for agent memory, source boundaries, durable result writeback, and lint.
life-log
Talk to Claude Code like a friend — a complaint or a quick note — and it auto-classifies, timestamps, and files each message into dated category notes, then gives you a suggestion. A UserPromptSubmit safety-net hook means nothing you say is ever lost. Local-first, plain markdown, no cloud.
obsidian-vault-kit
Full-lifecycle knowledge management toolkit for Obsidian vaults — ingest, lint, query, review, and sync.