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 AtlasOmnia/hermes-custom-pack --skill vault-organizationgit clone --depth 1 https://github.com/AtlasOmnia/hermes-custom-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/atlasomnia/hermes-custom-pack/vault-organization)<a href="https://agentmods.dev/skills/atlasomnia/hermes-custom-pack/vault-organization"><img src="https://agentmods.dev/badge/skills/atlasomnia/hermes-custom-pack/vault-organization/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/atlasomnia/hermes-custom-pack/vault-organization"><img src="https://agentmods.dev/badge/skills/atlasomnia/hermes-custom-pack/vault-organization.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.00057 | $0.01265 |
| Opus 5 | $0.00028 | $0.00633 |
| Sonnet 5 | $0.00011 | $0.00253 |
| Haiku 4.5 | $0.00006 | $0.00127 |
Grade A, and why
vault-organization 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 6d 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.
This is a copy
100% identical to vault-organization — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 74 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Vault Organization
Audit and reorganize the user's Obsidian vault. Run when asked to organize, clean up, or audit the vault structure — or to set up a sensible structure for a new/empty vault.
Vault path
Confirm the actual vault location first — do not assume ~/Documents/Obsidian Vault. Ask or check Obsidian's settings if the path is not known.
Structuring a vault (new or from scratch)
When the user asks "how should I organize my vault?" or is starting fresh, recommend a structure before touching anything. Use PARA as the default taxonomy — it maps cleanly onto how an assistant actually uses a vault:
- Projects/ — short-lived efforts with a goal and an end (a trip, a launch, a repair). One folder per project; archive when done.
- Areas/ — ongoing responsibilities with no end date (Health, Finance, Home, a business, a role). These persist and get maintained.
- Resources/ — reusable reference material not tied to one project: research, guides, templates, snippets, "how I do X."
- Archive/ — completed projects and superseded material, kept out of the active tree but searchable.
Conventions that make the vault work for both a human and an agent:
- MOCs (Maps of Content). Put an
MOC.md(orIndex.md) at each major folder root that links to its key notes. This is the table of contents the agent reads first to navigate. Keep MOCs updated when notes move. - Daily notes live in their own folder (e.g.
Journal/orDaily/) and are capture space, not organization space. Promote anything durable out of a daily note into its PARA home; don't let knowledge rot in dated files. - One canonical home per thing. A note lives in exactly one place. Link to it from elsewhere rather than duplicating it — duplicates drift.
- Names over cleverness. Plain, predictable folder and note names (
Areas/Health/, not02_Health_V2/). The agent finds things by reading names; make them say what's inside. - Generated artifacts stay out. The vault stores durable knowledge, not repeatable build/test output (screenshots, renders, Lighthouse runs, backups). Those go under
~/Projects/<project>-artifacts/<date>/with a pointer note in the vault.
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.
- 6d ago First seen · 74 lines · 57 tokens per session scan A 5711f1308609
vault-organization is a skill published in the GitHub repository AtlasOmnia/hermes-custom-pack (56 stars, last pushed 26d ago), licensed MIT. It adds 57 tokens to every session and 1,265 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to vault-organization, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
obshare-cli
Use when setting up obshare-cli 0.2.0, reviewing available commands, or choosing the right command for config, upload, permission, history, delete, and the plugin-first direct-share workflow.
session-artifact-indexing
Use this skill when a session creates or references several documents, trackers, plans, templates, source links, or skills that the user may need later.
obsidian
Use this skill for filesystem-first Obsidian vault work: reading notes, listing notes, searching note files, creating notes, appending content, and adding wikilinks.
google-workspace
Gmail, Calendar, Drive, Contacts, Sheets, and Docs — through Hermes-managed OAuth and a thin CLI wrapper. When gws is installed, the skill uses it as the execution backend for broader Google Workspace coverage; otherwise it falls back to the bundled Python client implementation.
notion
Notion API + ntn CLI: pages, databases, markdown, Workers.
obsidian-bases
Create and edit Obsidian Bases (.base files) with views, filters, formulas, and summaries. Use when working with .base files, creating database-like views of notes, or when the user mentions Bases, table views, card views, filters, or formulas in Obsidian.