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/upgradenpx skills add Skyfox-io/Memex --skill upgradegit 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/upgrade)<a href="https://agentmods.dev/skills/skyfox-io/memex/upgrade"><img src="https://agentmods.dev/badge/skills/skyfox-io/memex/upgrade.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 | $0.00058 | $0.02289 |
| Opus 5 | $0.00029 | $0.01144 |
| Sonnet 5 | $0.00012 | $0.00458 |
| Haiku 4.5 | $0.00006 | $0.00229 |
Grade A, and why
upgrade 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 — 171 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Memex - Upgrade
Wikilink rule: When referencing files in any markdown you write, use [[filename]] format.
Bring a workspace from any older Memex layout to the current one in a single, idempotent pass. The skill is a thin orchestrator over /memex:resummarize and /memex:reindex; it adds state detection (so re-runs are cheap) and sequencing (resummarize before reindex so closets entries inherit the v2 summary rules).
For the v1 → v2 upgrade specifically, see references/v1-to-v2.md. For the v2.0 → v2.1 increment, see references/v2-to-v2_1.md. Future major versions add their own playbooks under references/.
Step 0: Detect workspace, parse arguments
Run WORKSPACE_ROOT=$(pwd) && echo "$WORKSPACE_ROOT" via Bash.
Read _MANIFEST.md. If the file is missing or has no <!-- memex-managed marker, tell the user "Memex isn't managing this workspace yet. Run /memex:init to set up." and stop.
Acquire memory/.upgrade.lock and check the 24-hour cooldown in memory/.upgrade-runs.log. Both follow the shared bulk-write convention. See ../consolidate/references/locking.md.
Parse $ARGUMENTS:
--dry-run. Detect state and print the upgrade plan, but do not execute. Skip the lock acquisition.--force. Re-run every step regardless of state. Useful after a closets format change, or to verify cleanliness.
Step 1: Detect state
Read five signals from the workspace:
- Manifest version marker.
<!-- memex-managed:N.N.N -->from_MANIFEST.md. Compare to the current Memex VERSION. If older or missing, the workspace was scaffolded by an earlier Memex release. - Summary format version.
<!-- summary-format-version:N -->from_MANIFEST.md. If missing or< 2, summaries follow pre-v2 conventions and need/memex:resummarize. - Closets coverage. For each row in the Hub Map, check whether
<hub>/_CLOSETS.mdexists. Count hubs with coverage vs hubs without. - Closets format version. For each existing
_CLOSETS.md, read the<!-- memex-closets:N.N -->marker. If< 1.1and the hub has > 30 files, pagination needs to engage. - Memory closets (2.1+). Check whether
memory/_CLOSETS.mdexists. If missing on a manifest version< 2.1.0, this signals a v2.0 → v2.1 migration step.
What ships with it
2 files 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 · 171 lines · 58 tokens per session scan A f9f459d24ea8
upgrade is a skill published in the GitHub repository Skyfox-io/Memex (17 stars, last pushed 2mo ago), licensed MIT. It adds 58 tokens to every session and 2,289 once invoked, about $0.0003 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".