file-structure-creator

An agent for creating folders and empty atomic notes from a learning roadmap. Atomic notes are small notes focused on one topic.

In plain words
What is it for?
Use it after outlining a roadmap to create the corresponding folder structure and empty notes.
Why use it?
It creates the planned note structure in batches, so you do not have to make every folder and file by hand.

Agent

Install

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.

agentmods
npx agentmods add agents/easonnotsing/vaultforge/file-structure-creator
Clone the repo
git clone --depth 1 https://github.com/Easonnotsing/VaultForge
Per session 28 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,480 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin unknown No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00028 $0.01480
Opus 5 $0.00014 $0.00740
Sonnet 5 $0.00006 $0.00296
Haiku 4.5 $0.00003 $0.00148

Measured 2d ago against content hash 3ee9e37852e6, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

file-structure-creator 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 2d 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.

agents/file-structure-creator.md · 161 lines

The source is not reproduced here

No licence file

A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.

Read it on GitHub

Changes

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.

  1. 2d ago First seen · 161 lines · 28 tokens per session scan A 3ee9e37852e6

Subscribe to this mod's changes

file-structure-creator is an agent published in the GitHub repository Easonnotsing/VaultForge (11 stars, last pushed 3mo ago), with no licence file. It adds 28 tokens to every session and 1,480 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.

Related

Other agents, from other repositories

wiki-ingest

Read-only ingestion worker for one already-captured source. Reads the assigned source and relevant vault context, then returns evidence-grounded page drafts, expected hashes, and proposed paths to the parent orchestrator. It never writes or applies the shared transaction.

AgriciDaniel/claude-obsidian · 53 tokens

canvas-composer

Content strategist for canvas text nodes. Writes titles, descriptions, annotations, labels, and structured content for all canvas archetypes. Follows the 15-30 visible nodes per viewport principle. Content is scannable: headers, bullets, bold. Max 200 words per text node. Context: /canvas generate needs slide content…

AgriciDaniel/claude-canvas · 125 tokens

index

Kanonischer Einstieg in Agentenrollen und ihre Verantwortung im Demo-POS.

vincentmumme/personalos-boilerplate · 0 tokens

pkm-capture

Use proactively in the background after completing significant work blocks, after git commits (triggered automatically by PreToolUse hook), or before session ends. Captures session work into the PKM vault: devlog entries, decisions, research findings, tasks, and bug documentation. Conservative — most exchanges produce…

AdrianV101/obsidian-pkm-plugin · 476 tokens

vault-explorer

Use proactively when researching what the vault knows about a topic, before creating new notes, or when exploring existing knowledge and connections. Run in foreground — results inform the caller's next steps. Examples: Context: User asks about a topic before creating new content. user: "What does the vault already…

AdrianV101/obsidian-pkm-plugin · 252 tokens

review-prep

Aggregate performance review material from the vault for a given period. Scans wins doc, decisions led, incidents handled, competency evidence, 1-on-1 feedback, and work evidence. Invoke via /brief or when the user asks for review prep.

superuser-pal/awesome-second-brain · 54 tokens