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 Skyfox-io/Memex --skill add-domaingit clone --depth 1 https://github.com/Skyfox-io/MemexWrote 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/skyfox-io/memex/add-domain)<a href="https://agentmods.dev/skills/skyfox-io/memex/add-domain"><img src="https://agentmods.dev/badge/skills/skyfox-io/memex/add-domain.svg" alt="Measured on agentmods" 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.00038 | $0.01278 |
| Opus 5 | $0.00019 | $0.00639 |
| Sonnet 5 | $0.00008 | $0.00256 |
| Haiku 4.5 | $0.00004 | $0.00128 |
Grade A, and why
add-domain 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 8d 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 — 101 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Memex - Add Domain
Wikilink rule: Use [[filename]] for every file reference in markdown.
Create a domain folder with a hub index and a closets file, optionally migrate matching files into it, and wire it into _MANIFEST.md.
Step 1: Validate workspace
Run WORKSPACE_ROOT=$(pwd) && echo "$WORKSPACE_ROOT" via Bash.
Read _MANIFEST.md. If missing: tell the user "No manifest found. Run /memex:init first." and stop.
Step 2: Get the domain name
If $ARGUMENTS is set, use it. Otherwise ask. Convert to slug (lowercase, hyphens, no spaces).
Step 3: Scan for files that belong in this domain
Scan the workspace for existing files about this topic (by content, not filename). If found, list them and ask whether to move them in. On confirmation, move and update [[wikilinks]] in other files that referenced the old paths.
Step 4: Create the folder and closets file
Create [domain-name]/ at the workspace root (or inside the established domains parent if existing Hub Map entries use one).
Create [domain-name]/_CLOSETS.md. Format and per-entry typed-field schema (subjects, people, claims, decisions, dates, status) are canonical at memex/skills/session-end/references/closets-format.md. Per-entry summary fields follow the 8 rules at memex/skills/session-end/references/summary-rules.md. Use templates/closets.md.tmpl from the init skill for the file header.
If files were moved in Step 3, add a closets entry per file populated from its content.
Optional: prose hub index
By default, domains are closets-only (the typed-field index handles retrieval). An optional prose [domain-name]-index.md can also be created for human-facing context: domain philosophy, "how we work here" preamble, ad-hoc notes that don't fit typed rows. Skipped by default.
If the user explicitly asks for a hub index, or the domain has prose context worth preserving (e.g., a long-form doc migrated from elsewhere), create [domain-name]/[domain-name]-index.md:
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.
- 8d ago First seen · 101 lines · 38 tokens per session scan A 34fa21c79cf2
add-domain is a skill published in the GitHub repository Skyfox-io/Memex (17 stars, last pushed 2mo ago), licensed MIT. It adds 38 tokens to every session and 1,278 once invoked, about $0.0002 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
setup-brain
Set up or upgrade an AI-powered Obsidian vault. Interviews you, builds your vault structure (or works with what you already have), creates your CLAUDE.md memory file, installs tools, and gets you journaling — all in one conversation. Also has a repair/upgrade path for existing users.
second-brain-mapping
Use when the user wants to map or remap their second brain, refresh the vault's queryable metadata index, extract structured frontmatter from typed notes (books, meetings, people, journals, goals), fill wikilink gaps, or surface cross-type insights and patterns no single file shows. Triggers: /second-brain-mapping…
evolve
Use when many related hardened instincts (high-confidence feedback/discovery memories) have piled up in one domain, when the user runs /evolve or asks to promote, cluster, graduate, or consolidate accumulated instincts into a Command, Skill, or Agent, or when files in Instinct Proposals need review. Part of the…
vault-system
Use when maintaining the vault ITSELF as a system, not its content: knowledge-graph build/rebuild/query (graphify), second-brain mapping, vault diagnose/audit/hygiene, drift detection, extract rules from vault, backfill journals, setup vault types, consolidate memory (index over cap), Obsidian tooling…
diagnose
Use when an AI Brain vault needs a health check or something feels off: Claude ignores CLAUDE.md, journal entries missing from /weekly, hooks not firing, something broke after a git pull, a friend's install misbehaves, Obsidian crashes or pegs the CPU, a .claude/worktrees folder appeared, Granola/WhatsApp/Slack/Gmail…
solopreneur-context
When the user wants to set up or update their solopreneur context document — a one-time profile of their business that all other skills reference automatically. Use when the user says "set up my context," "tell you about my business," "save my business info," "update my profile," or when starting a new session and…