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 lexbritvin/obsidian-skills-pack --skill obsidian-graphgit clone --depth 1 https://github.com/lexbritvin/obsidian-skills-packWrote 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/lexbritvin/obsidian-skills-pack/obsidian-graph)<a href="https://agentmods.dev/skills/lexbritvin/obsidian-skills-pack/obsidian-graph"><img src="https://agentmods.dev/badge/skills/lexbritvin/obsidian-skills-pack/obsidian-graph/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/lexbritvin/obsidian-skills-pack/obsidian-graph"><img src="https://agentmods.dev/badge/skills/lexbritvin/obsidian-skills-pack/obsidian-graph.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.00146 | $0.06026 |
| Opus 5 | $0.00073 | $0.03013 |
| Sonnet 5 | $0.00029 | $0.01205 |
| Haiku 4.5 | $0.00015 | $0.00603 |
Grade B, and why
obsidian-graph scanned grade B with 1 finding 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
4. **Measure vault size:** `find . -name '*.md' -not -path './.obsidian/*' -not -path './.trash/*' -not -path './.claude/*' | wc -l`. Forces depend on this. How it starts
The opening of the file, as written. The whole thing — 466 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Obsidian Graph view
Global graph configuration lives in .obsidian/graph.json. Local graph (Graph view opened from a single note) lives in .obsidian/workspace.json and does not inherit from global. This skill covers global graph unless explicitly noted.
For diagnosing what's wrong with a graph (over-connection, render-only edges, false categories), use the paired obsidian-graph-audit skill first.
Workflow when the user asks "configure my graph"
- Ask or read intent first. What's bothering them, or what do they want to see? Color groups without a goal are pure aesthetics — skip them.
- ⚠️ Have the user close Graph view (or quit Obsidian). This is mandatory — Obsidian rewrites
graph.jsonwhen Graph view closes, wiping external edits. See Caveats. - Read the current
.obsidian/graph.json. Don't reset settings the user has tuned (especiallyscale). - Measure vault size:
find . -name '*.md' -not -path './.obsidian/*' -not -path './.trash/*' -not -path './.claude/*' | wc -l. Forces depend on this. - Apply minimum changes, explain each. 14 color groups on 600 notes is too many — 3-8 is the proven range.
- Keep only what adds signal. Filter > group when you don't want to see something; group > filter when you want to differentiate.
- Verify decimal RGB math. A wrong byte in a color value silently renders as a different color. Always round-trip HEX↔decimal (see below).
- Have the user open Graph view after edits. Changes take effect on next open.
Full schema of graph.json
20 fields. Source: community gist on syncing graph settings, example repo. Obsidian has no official schema document.
Filters block
| Field | Type | Purpose |
|---|---|---|
collapse-filter |
bool | Whether the Filters block is collapsed in the UI |
search |
string | Filter query (same syntax as core Search) |
showTags |
bool | Tag nodes shown as separate nodes |
showAttachments |
bool | Files (PNG, PDF) shown as nodes |
hideUnresolved |
bool | Hide unresolved wikilinks |
showOrphans |
bool | Show nodes with no connections |
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 · 466 lines · 146 tokens per session scan B 9c2dfa37693d
obsidian-graph is a skill published in the GitHub repository lexbritvin/obsidian-skills-pack (2 stars, last pushed 5d ago), licensed MIT. It adds 146 tokens to every session and 6,026 once invoked, about $0.0007 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
plannotator-visual-explainer
Generate self-contained HTML visualizations with Plannotator theming. Use for implementation plans, PR explainers, architecture diagrams, data tables, slide decks, and any visual explanation of technical concepts. Plans and PR explainers follow Plannotator's prescriptive approach; all other visual content delegates to…
plannotator-annotate
Open Plannotator's annotation UI for a file, folder, or URL, then address the returned annotations.
obsidian-layout-adjustment
Workflow for working with the user on changing how Obsidian looks using CSS snippets. Use this whenever the user asks to restyle Obsidian, tune a vault's visual layout, adjust tabs, sidebars, note surfaces, properties, backlinks, graph panes, file explorer rows, icons, links, shadows, active states, or CSS snippets.…
obsidian-ref
Technical references, manifest rules, file formats, and UX guidelines for Obsidian. Load when checking API details, manifest requirements, or UI/UX standards.
obsidian-theme-dev
CSS/SCSS development patterns for Obsidian themes. Load when working with theme.css, SCSS variables, or CSS selectors.
jtbd-to-interface
A method for turning user jobs—the outcomes people need to achieve—into a screen and navigation specification.