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 agentmods add skills/skyfox-io/memex/link-workspacenpx skills add Skyfox-io/Memex --skill link-workspacegit 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/link-workspace)<a href="https://agentmods.dev/skills/skyfox-io/memex/link-workspace"><img src="https://agentmods.dev/badge/skills/skyfox-io/memex/link-workspace.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.00030 | $0.00570 |
| Opus 5 | $0.00015 | $0.00285 |
| Sonnet 5 | $0.00006 | $0.00114 |
| Haiku 4.5 | $0.00003 | $0.00057 |
Grade A, and why
link-workspace 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 5d 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 — 51 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Memex - Link Workspace
Wikilink rule: When referencing any file in markdown, always use [[filename]] wikilink format.
Register the current workspace in ~/.memex/sources.md. Registry conventions, script-path resolution, and privacy semantics live in memex/skills/cross-search/references/registry.md. CLI surface: ${CLAUDE_SKILL_DIR}/scripts/sources.py.
Step 0: Validate workspace
WORKSPACE_ROOT=$(pwd). Read _MANIFEST.md. If absent, tell the user "No manifest found. Run /memex:init first." and stop.
Step 1: Source name
Use $ARGUMENTS if provided. Otherwise propose a slug-ified default from the workspace folder name and ask to confirm. Names should be short, slug-style, and meaningful across workspaces (e.g., nonprofit-foundation, personal, dashflow).
Step 2: Register
python3 "${CLAUDE_SKILL_DIR}/scripts/sources.py" add <source-name> <WORKSPACE_ROOT>
If the script reports the name is taken: tell the user "A source named '' is already registered (run python3 "${CLAUDE_SKILL_DIR}/scripts/sources.py" list to see all). Pick a different name or /memex:unlink-workspace <name> first."
Step 3: Confirm
Linked: <source-name> → <WORKSPACE_ROOT>
Searchable: yes (default)
Searchable from other workspaces via:
/memex:cross-search <query>
Opt out:
python3 "${CLAUDE_SKILL_DIR}/scripts/sources.py" set-searchable <source-name> false
Gotchas
- Path is captured at link time, absolute. If the workspace later moves, the registry entry breaks silently. Cross-search will report "path missing". Re-link after moves.
- Not idempotent. Re-running with the same name errors out instead of updating. To change the path, unlink then re-link.
_MANIFEST.mdmissing only warns, doesn't block at the script layer. This skill validates first so the user gets a clearer message. Don't skip Step 0.- Symlinked workspace roots are resolved to their real path by the script. If you link via a symlink, the registry shows the resolved target.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 5d ago First seen · 51 lines · 30 tokens per session scan A 2b460fecbac2
link-workspace is a skill published in the GitHub repository Skyfox-io/Memex (17 stars, last pushed 2mo ago), licensed MIT. It adds 30 tokens to every session and 570 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
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…
obsidian-companion
Use when interacting with the user's Obsidian vault — reading, writing, searching, or chatting with notes using local RAG. Guides tool selection and writing strategy for all vault operations.
wiki-ingest
Use when the user wants to ingest external sources into the vault — PDFs, markdown files, transcripts, Readwise exports, or any document. Triggers on "ingest", "process document", "import into vault", "distill this", "add to vault", or "extract knowledge from".
vault-lint
Use when the user wants a health audit of the vault — stale content, provenance drift, frontmatter compliance, or MOC coverage gaps. Triggers on "lint vault", "vault health", "check vault", "stale notes", "vault audit", "vault quality", or "check conventions".
compound
Use when the user wants to promote cross-project knowledge to the global Engineering/ folder, or says "promote knowledge", "compound notes", "knowledge synthesis", or "find repeated ideas across projects".
links
Use when the user wants to explore connections between notes, see what links to or from a note, or says "links", "backlinks", "connections", or "graph".