Borrowing it
Nothing to install: this file belongs to AlexisBalayre/claude-code-power-config. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/AlexisBalayre/claude-code-power-config/main/.claude/skills/obsidian-vault/SKILL.mdgit clone --depth 1 https://github.com/AlexisBalayre/claude-code-power-configWrote 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/alexisbalayre/claude-code-power-config/obsidian-vault)<a href="https://agentmods.dev/skills/alexisbalayre/claude-code-power-config/obsidian-vault"><img src="https://agentmods.dev/badge/skills/alexisbalayre/claude-code-power-config/obsidian-vault/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/alexisbalayre/claude-code-power-config/obsidian-vault"><img src="https://agentmods.dev/badge/skills/alexisbalayre/claude-code-power-config/obsidian-vault.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.00044 | $0.00573 |
| Opus 5.5 | $0.00018 | $0.00229 |
| Sonnet 5.5 | $0.00009 | $0.00115 |
| Haiku 4.5 | $0.00004 | $0.00057 |
Grade A, and why
obsidian-vault 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 2mo 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
Obsidian Vault
A personal-workflow integration. It assumes your notes live in an Obsidian vault on disk and operates on them with the standard Read/Glob/Grep tools plus shell.
Vault location
Set OBSIDIAN_VAULT in .env (see .env.example), then source it in your shell
(set -a; . ./.env; set +a) so the commands below resolve $OBSIDIAN_VAULT:
# .env
OBSIDIAN_VAULT="$HOME/Documents/notes" # adjust to your vault
Typical subfolders (rename to match yours):
Daily Logbook/: daily notes (managed by/daily-note)Templates/: note templates (e.g.,Daily Log.md)
Naming conventions
- Index notes: aggregate related topics (e.g.,
Skills Index.md,RAG Index.md) - Title Case for all note names
- Daily notes use
YYYY-MM-DD.mdand live underDaily Logbook/
Linking
- Use Obsidian
[[wikilinks]]syntax:[[Note Title]] - Notes link to dependencies/related notes at the bottom
- Index notes are just lists of
[[wikilinks]]
Workflows
Search for notes
# Search by filename
find "$OBSIDIAN_VAULT" -name "*.md" | grep -i "keyword"
# Search by content
grep -rl "keyword" "$OBSIDIAN_VAULT" --include="*.md"
Or use the Grep/Glob tools directly on $OBSIDIAN_VAULT.
Create a new note
- Use Title Case for the filename
- Write content as a unit of learning
- Add
[[wikilinks]]to related notes at the bottom - Place it in the appropriate subfolder (or the vault root for general index/topic notes)
Find related notes
Search for [[Note Title]] across the vault to find backlinks:
grep -rl "\\[\\[Note Title\\]\\]" "$OBSIDIAN_VAULT"
Find index notes
find "$OBSIDIAN_VAULT" -name "*Index*"
Related
- The
/daily-noteskill manages theDaily Logbook/subfolder; defer to it for daily notes.
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.
- 2mo ago First seen · 76 lines · 44 tokens per session scan A 4d7746425aa3
obsidian-vault is a skill published in the GitHub repository AlexisBalayre/claude-code-power-config (2 stars, last pushed 1mo ago), licensed MIT. It adds 44 tokens to every session and 573 once invoked, about $0.0002 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-31.
Other skills, from other repositories
send-email
Compose and send a one-off email to a named recipient via Resend - written in the operator's voice, then sent in-run through the shared send caps with an operator audit copy.
caveman-help
Quick-reference card for all caveman modes, skills, and commands. One-shot display, not a persistent mode. Trigger: /caveman-help, "caveman help", "what caveman commands", "how do I use caveman".
get-started
First-run setup for the Aeon plugin. Checks the connection to the user's Aeon agent, shows what it can do, and runs one skill so the user sees it work. Use right after the plugin is installed, or when the user asks how to get started with Aeon.
skill-factory
A workflow that examines completed session work and turns reusable patterns into Claude Code skills.
session-wrap
Use when wrapping up a session before ending. 4 parallel subagents detect doc updates, repeated patterns, learning points, and follow-ups, then a verifier deduplicates and presents choices. Triggers on /session-wrap, session wrap, session cleanup, end of session.
toolbox
Pre/post dev toolbox — named bundles of skills/agents loaded before development work and councils of experts invoked after. Run /toolbox or the toolbox.py CLI to list, activate, initialize, export, import, and validate toolboxes. Invoke at the start or end of a dev session, when setting up a new repo, or when sharing…