add-module
Skill2 starsChanged 6 months agoMITView on GitHub
Scaffold a new vault module (like Books, Goals, Recipes) with a top-level folder, AGENTS.md, and Templater template.
10 other projects use a version of this.
Adopted by
Most recently taken up by
- testcontainers/testcontainers-javatheir own version, first seen Nov 16, 2026
- helmut-hoffer-von-ankershoffen/heinzeltheir own version, first seen Nov 8, 2026
- heytcass/claudeostheir own version, first seen Oct 29, 2026
- Cassius2584/claude-uni-workspacetheir own version, first seen Oct 22, 2026
- testcontainers/testcontainers-nodetheir own version, first seen Oct 17, 2026
- ai-erp-collab/deterministic-context-routing-plugintheir own version, first seen Oct 15, 2026
Other versions10 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 10
- testcontainers/testcontainers-java★ 8.8ksame name
- fullstackhero/dotnet-starter-kit★ 6.9ksame name
- testcontainers/testcontainers-node★ 2.6ksame name
- Cassius2584/claude-uni-workspace★ 5same name
- helmut-hoffer-von-ankershoffen/heinzel★ 2same name
- AURORA-NEURO/aurora-agent★ 1same name
- heytcass/claudeos★ 1same name
- ai-erp-collab/deterministic-context-routing-plugin★ 0same name
- alimranfakir/Claude_skills★ 0same name
- shubhsha/ai-engineer-2030★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository20 other files it gives its agents.
- 1-Projects/AGENTS.mdAGENTS.md
- 2-Areas/AGENTS.mdAGENTS.md
- 3-Resources/AGENTS.mdAGENTS.md
- 4-Archive/AGENTS.mdAGENTS.md
- _admin/AGENTS.mdAGENTS.md
- _agent/AGENTS.mdAGENTS.md
- Books/AGENTS.mdAGENTS.md
- Content/AGENTS.mdAGENTS.md
- Dashboard/AGENTS.mdAGENTS.md
- Goals/AGENTS.mdAGENTS.md
- Granola/AGENTS.mdAGENTS.md
- Inbox/AGENTS.mdAGENTS.md
- Journal/AGENTS.mdAGENTS.md
- People/AGENTS.mdAGENTS.md
- Recipes/AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- close-daySkill
- daily-recapSkill
- ingest-meetingSkill
- todaySkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
16 rules. 0 are common, 8 are distinctive, and 8 are very specific to this project.
0
Common
Most of the 9 edited versions we read keep these.
8
Distinctive
This author's own choices. Worth a look.
8
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 9
Create a new vault module - a top-level folder with its own AGENTS.md and Templater template, like the existing Books, Goals, People, …
- Distinctive: line 17
Ask the user in one message:
- Distinctive: line 39
Wait for the user to confirm or request changes.
- Very specific: line 45
Create <Module Name>/ at the vault root.
- Very specific: line 49
Write <Module Name>/AGENTS.md following the existing pattern.
- Distinctive: line 68
Only include Statuses if the module has a status workflow
- Distinctive: line 69
Only include Properties if there are non-obvious fields worth documenting
- Distinctive: line 70
Agent rules: should always include "Don't create or modify entries without being asked" unless the user says otherwise
- Distinctive: line 71
Always end with the Templates line pointing to the template path
- Very specific: line 75
Write to _admin/templates/para/<Module Name>.md (or _admin/templates/<subfolder>/ if the user prefers a different location).
- Very specific: line 103
Use <% tp.file.title %> for the note title
- Very specific: line 104
Use <% tp.date.now("YYYY-MM-DD") %> for dates
- Very specific: line 108
Create <Module Name>/<Module Name> Dashboard.md with Dataview queries that list all entries in the module.
- Distinctive: line 125
Add additional filtered views if the module has statuses (e.g.
- Very specific: line 129
CLAUDE.md: - Add the new module to the folder map in the ## What code block. - Very specific: line 135
Dashboard/Dashboard Home.md: - Add a link to the module dashboard on the bottom navigation line (line 45).
“Common” is measured: kept by at least 6 in 10 of the 9 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Add Module
Create a new vault module - a top-level folder with its own AGENTS.md and Templater template, like the existing Books, Goals, People, Recipes, and Content modules.
Arguments
$ARGUMENTS may contain the module name. If not provided, ask.
Step 1: Gather info
Ask the user in one message:
- Module name (if not in arguments) - becomes the folder name
- One-line description - what is this module for?
- Properties - frontmatter fields specific to this module (e.g. Books has
author, status, rating, genre, format). Ask for field names and any default values. - Statuses (optional) - if entries have a lifecycle, what are the stages? (e.g. Books:
to-read -> reading -> read) - Body sections - what sections should new entries have? (e.g. Books has "Why Read This, Reading Log, Key Takeaways, Notes, Rating")
- Dataview queries (optional) - should entries show related projects, people, tasks, or other linked content?
- Agent rules - how should the agent interact with this module? Default: "Read for context. Don't create or modify entries without being asked."
Skip questions the user has already answered.
Step 2: Confirm
Show the user exactly what will be created:
- Folder:
<Module Name>/ - AGENTS.md - show the full draft
- Template:
_admin/templates/para/<Module Name>.md- show the full draft - Dashboard:
<Module Name>/<Module Name> Dashboard.md- show the draft - Registrations: changes to
CLAUDE.mdandDashboard/Dashboard Home.md
Wait for the user to confirm or request changes.
Step 3: Create
3a. Create the folder
Create <Module Name>/ at the vault root.
3b. Create AGENTS.md
Write <Module Name>/AGENTS.md following the existing pattern. Structure:
# <Module Name>
<One-line description.>
**Statuses:** `status-a` -> `status-b` -> `status-c`
**Properties:** <list of key frontmatter fields and their meaning>
<Any additional notes about how the module works - integrations, special behaviors, etc. Keep it brief.>
**Agent rules:** <How the agent should interact with this module.>
**Templates:** `_admin/templates/para/<Module Name>.md`Rules for writing AGENTS.md:
- Match the tone of existing ones: terse, factual, no fluff
- Only include Statuses if the module has a status workflow
- Only include Properties if there are non-obvious fields worth documenting
- Agent rules should always include "Don't create or modify entries without being asked" unless the user says otherwise
- Always end with the Templates line pointing to the template path
3c. Create the Templater template
Write to _admin/templates/para/<Module Name>.md (or _admin/templates/<subfolder>/ if the user prefers a different location).
Template structure:
---
created: <% tp.date.now("YYYY-MM-DD") %>
type: <module-name-lowercase>
tags:
- type/<module-name-lowercase>
<custom properties with defaults or empty values>
archived: false
source: human
---
# <% tp.file.title %>
<body sections as specified by the user>Rules for templates:
created,type,tags,archived,sourceare always present- Custom properties go between
tagsandarchived - Status fields get their default value (usually the first status in the workflow)
- Empty properties use blank value (no quotes, just empty)
- Boolean properties default to
false - Body uses
##headings for sections - Dataview queries use the standard format from existing templates (match
FROM,WHERE,SORTpatterns) - Use
<% tp.file.title %>for the note title - Use
<% tp.date.now("YYYY-MM-DD") %>for dates
3d. Create the module dashboard
Create <Module Name>/<Module Name> Dashboard.md with Dataview queries that list all entries in the module. Follow the pattern of existing dashboards (e.g. Books Dashboard, Recipes Dashboard).
Basic structure:
# <Module Name>
## All <Module Name>
\```dataview
TABLE WITHOUT ID file.link AS "<Entry Type>", status
FROM "<Module Name>"
WHERE type = "<module-name-lowercase>" AND !contains(file.name, "AGENTS") AND !contains(file.name, "Dashboard")
SORT file.mtime DESC
\```Add additional filtered views if the module has statuses (e.g. "Active", "Completed" sections).
3e. Register the module
CLAUDE.md - Add the new module to the folder map in the ## What code block. Insert it alphabetically among the standalone modules (after the PARA folders, before _admin and _agent). Follow the existing format:
<Module Name>/ → <One-line description>Dashboard/Dashboard Home.md - Add a link to the module dashboard on the bottom navigation line (line 45). Follow the existing format:
[[<Module Name>/<Module Name> Dashboard|<Module Name>]]Append it after the last module link, before the Agent KB link.
Step 4: Log
Append to _agent/log.md:
## [YYYY-MM-DD] module | Added <Module Name>
- Created `<Module Name>/AGENTS.md`
- Created `<Module Name>/<Module Name> Dashboard.md`
- Created `_admin/templates/para/<Module Name>.md`
- Registered in `CLAUDE.md` and `Dashboard/Dashboard Home.md`
- Properties: <list>
- Statuses: <workflow or "none">Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

