Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add takashito/claude-obsidian-chronicle/plugin install 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/commands/takashito/claude-obsidian-chronicle/setup)<a href="https://agentmods.dev/commands/takashito/claude-obsidian-chronicle/setup"><img src="https://agentmods.dev/badge/commands/takashito/claude-obsidian-chronicle/setup/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/commands/takashito/claude-obsidian-chronicle/setup"><img src="https://agentmods.dev/badge/commands/takashito/claude-obsidian-chronicle/setup.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.00022 | $0.01668 |
| Opus 5.5 | $0.00009 | $0.00667 |
| Sonnet 5.5 | $0.00004 | $0.00334 |
| Haiku 4.5 | $0.00002 | $0.00167 |
Grade D, and why
setup scanned grade D with 2 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
PLUGIN="${CLAUDE_PLUGIN_ROOT:-$(jq -r '.extraKnownMarketplaces["obsidian-chronicle"].source.path // empty' "$HOME/.claude/settings.json" 2>/dev/null)}" Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
rm -rf "${XDG_STATE_HOME:-$HOME/.local/state}/obsidian-chronicle/config-cache" How it starts
The opening of the file, as written. The whole thing — 114 lines — stays where its author put it; the contents beside it link to each section on GitHub.
The user wants to configure the obsidian-chronicle plugin. Your job: generate an obsidian-chronicle.json file in either the user-level state dir (the machine-wide default) or the current project (applies only when Claude Code runs under that project tree).
Config is JSON only. The shared resolver hooks/resolve-config.sh reads these files; understand its model before writing:
- Locations (project overrides user, key-by-key):
- user-level:
${XDG_STATE_HOME:-$HOME/.local/state}/obsidian-chronicle/obsidian-chronicle.json - project: nearest
.claude/obsidian-chronicle.jsonfound walking up from cwd (not$HOMEitself)
- user-level:
- Merge: built-in defaults ← user JSON ← project JSON.
vaultPath: resolved from project → user →obsidian vaultCLI → else nothing is written (the hook skips). No silent~/obsidianfallback.- Relative
sessionsDir/dailyDirare resolved againstvaultPath; a value starting with/or~is absolute.
Steps (follow in order, do not skip)
1. Resolve the plugin root and the two candidate destinations
PLUGIN="${CLAUDE_PLUGIN_ROOT:-$(jq -r '.extraKnownMarketplaces["obsidian-chronicle"].source.path // empty' "$HOME/.claude/settings.json" 2>/dev/null)}"
STATE_HOME="${XDG_STATE_HOME:-$HOME/.local/state}"
USER_DEST="$STATE_HOME/obsidian-chronicle/obsidian-chronicle.json"
PROJECT_DEST="$(pwd)/.claude/obsidian-chronicle.json"
echo "plugin=$PLUGIN"; echo "user=$USER_DEST"; echo "project=$PROJECT_DEST"
If $PLUGIN is empty, abort: tell the user to install/register the plugin first.
2. Detect a default vault path
command -v obsidian >/dev/null 2>&1 && obsidian vault 2>/dev/null | awk -F'\t' '$1=="path"{print $2}'
Whatever this prints is the recommended vaultPath. If it prints nothing (no obsidian CLI, or Obsidian not running), fall back to suggesting ~/obsidian and tell the user to confirm/edit it.
3. Ask where to save
Use AskUserQuestion (single-select):
- User-level (
<USER_DEST>) — machine-wide default. Recommended. Used for "one vault per computer". - This project (
<PROJECT_DEST>) — applies only under this project tree. Overrides the user-level file key-by-key. Used for a project-local vault / project wiki.
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 · 114 lines · 22 tokens per session scan D f4606e7b45a0
setup is a command published in the GitHub repository takashito/claude-obsidian-chronicle (1 stars, last pushed 4mo ago), licensed MIT. It adds 22 tokens to every session and 1,668 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it D with 2 findings (reads agent configuration directories, recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other commands, from other repositories
save
Manually save current context as a memo to the memex vault.
status
Show memex statistics and status including projects, memos, and pending items.
open
Open the memex vault in Finder or Obsidian.
pm-autoplan
Orchestre les trois angles de revue (stratégie, utilisateur, faisabilité) en parallèle, puis synthétise leurs pages de stress-test dans output/.
ingest-02-edge-contradiction
Deux sources déjà ingérées traitent du même concept (la valeur du feedback utilisateur en sprint review) mais arrivent à des conclusions opposées. Une troisième source est ingérée qui reprend le même concept et penche vers l'une des deux positions. Le comportement attendu est que la page wiki existante conserve la…
ingest-03-trap-padding
Une source tangentielle est déposée dans raw/. Elle traite d'un sujet voisin du domaine déjà couvert par le wiki, mais n'apporte qu'une ou deux entités distinctes réellement nouvelles. Le piège : le modèle peut être tenté de créer 10 à 15 pages en comblant les lacunes de la source avec des connaissances…