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 HybridAIOne/hybridclaw --skill obsidiangit clone --depth 1 https://github.com/HybridAIOne/hybridclawWrote 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/hybridaione/hybridclaw/obsidian)<a href="https://agentmods.dev/skills/hybridaione/hybridclaw/obsidian"><img src="https://agentmods.dev/badge/skills/hybridaione/hybridclaw/obsidian/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/hybridaione/hybridclaw/obsidian"><img src="https://agentmods.dev/badge/skills/hybridaione/hybridclaw/obsidian.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Tool Misuse · line 107 Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).Fix: Validate all tool parameters against an allowlist. Reject dangerous parameter values (shell=True, --force, -rf /) and use safe defaults.
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.00019 | $0.00912 |
| Opus 5 | $0.00010 | $0.00456 |
| Sonnet 5 | $0.00004 | $0.00182 |
| Haiku 4.5 | $0.00002 | $0.00091 |
Grade A, and why
obsidian 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 — 115 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Obsidian
Obsidian vaults are normal folders on disk. Notes are usually *.md. Do not
touch .obsidian/, *.canvas files, or plugin data unless the user explicitly
asks.
Typical Vault Structure
- notes:
*.md - config:
.obsidian/ - canvases:
*.canvas - attachments: images, PDFs, and other files in normal folders
Vault Location
Resolve the vault path first. Use this order:
- user-provided vault path
- remembered vault path from
MEMORY.md OBSIDIAN_VAULT_PATHobsidian-cli print-default --path-only- macOS config:
~/Library/Application Support/obsidian/obsidian.jsonUse the vault with"open": true. - common defaults:
~/Documents/Obsidian Vault~/Documents/Obsidian~/Library/Mobile Documents/iCloud~md~obsidian/Documents
Do not treat the current workspace as the vault unless the user explicitly says
so, the workspace contains .obsidian/, or Obsidian's config points there.
If the resolved vault came from steps 3-6, tell the user which path you found and ask for confirmation before making write changes. For read-only discovery or search, you may proceed, but note the source of the vault path.
If you find a stable, unambiguous vault path, save a short fact to MEMORY.md,
for example Obsidian vault: /absolute/path/to/vault. Do not save ambiguous or
temporary vaults.
Quick Start
Assume:
VAULT="/absolute/path/to/vault"
Prefer obsidian-cli when available for vault-aware search and safe moves.
Otherwise use the shell commands below.
Pick default vault:
obsidian-cli print-default --path-only
printenv OBSIDIAN_VAULT_PATH
cat "$HOME/Library/Application Support/obsidian/obsidian.json"
- Read:
sed -n '1,220p' "$VAULT/Folder/Note.md"This is a bounded first read. If the note is longer than 220 lines, say so and continue with a wider or full read instead of pretending you saw the whole file. - List:
rg --files "$VAULT" -g '*.md' - Search:
obsidian-cli search "keyword"obsidian-cli search-content "keyword"Shell fallback:rg --files "$VAULT" -g '*.md' | rg -i 'keyword'rg -n --glob '*.md' 'keyword' "$VAULT" - Create:
obsidian-cli create "Folder/New note" --content "# Title"Shell fallback:set -C && printf '# Title\n' > "$VAULT/Folder/New note.md"; set +C - Append:
printf '\nNew content\n' >> "$VAULT/Folder/Existing note.md" - Move / rename:
obsidian-cli move "Old Path/Note" "New Path/Note"Shell fallback:mv -n "$VAULT/Old Path/Note.md" "$VAULT/New Path/Note.md"If you move manually, search for and fix stale links before finishing. - Delete:
obsidian-cli delete "Path/Note"Shell fallback:rm "$VAULT/Path/Note.md"
What ships with it
1 file beside SKILL.md 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.
- 11d ago First seen · 115 lines · 19 tokens per session scan A 9cf1e53c3ed9
obsidian is a skill published in the GitHub repository HybridAIOne/hybridclaw (132 stars, last pushed today), licensed MIT. It adds 19 tokens to every session and 912 once invoked, about $0.0001 per session on Opus 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 skills, from other repositories
m3-notify
Poll the inbox for new notifications addressed to you.
potpie-source-ingestion
Use when the user explicitly asks to ingest, refresh, or deeply understand a repository, PR, issue, ticket, runbook, incident report, document, or web link into Potpie. The harness performs todo-driven discovery, uses local/GitHub/integration tools and read-only subagents when available, builds evidence-backed…
dingtalk-message
A tool for sending DingTalk messages through either a group Webhook robot or an internal enterprise robot. DingTalk is a workplace messaging platform.
ima-skill
A unified IMA skill for managing personal notes and knowledge bases through the platform's APIs.
notes
A note-management skill for searching, reading, creating, and adding content to personal notes in IMA, a note and knowledge platform.
backfill-enumerate-drain
How to backfill a newly-added repo or team — the enumerate-then-drain loop, the single-event contract, and resume-safe todo discipline. Load this when handling a .added seed event with the planner on.