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/archivenpx skills add Skyfox-io/Memex --skill archivegit 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/archive)<a href="https://agentmods.dev/skills/skyfox-io/memex/archive"><img src="https://agentmods.dev/badge/skills/skyfox-io/memex/archive.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.00057 | $0.00718 |
| Opus 5 | $0.00028 | $0.00359 |
| Sonnet 5 | $0.00011 | $0.00144 |
| Haiku 4.5 | $0.00006 | $0.00072 |
Grade A, and why
archive 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 4d 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 — 64 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Memex - Archive
Wikilink rule: Use [[filename]] for every file reference in markdown.
Move a file from Tier 2 to Tier 3 in _MANIFEST.md and update its hub status. The file stays on disk; archiving just stops auto-loading.
Step 1: Find workspace root
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: Identify the file
If $ARGUMENTS is set, use it. Otherwise read the Tier 2 sections from _MANIFEST.md, show the entries, and ask which to archive.
Step 3: Move in manifest
- Remove the file's row from its Tier 2 domain section.
- Add to the Tier 3 table with today's date and a brief reason:
| [[filename]] | [why archived] | YYYY-MM-DD |
Step 4: Update the hub and closets
Read the relevant domain hub. Set the file's status to Archived, or remove it from the active table.
Then update the file's entry in <domain>/_CLOSETS.md (or _CLOSETS-archive.md if it lives there per pagination). Change the entry's status: line to status: archived. If the file has no closets entry yet, skip. Session-end will not re-create it for an archived file.
Closets schema and field semantics: memex/skills/session-end/references/closets-format.md.
Step 5: Confirm
Archived: [filename]
From: Tier 2 ([domain name])
Reason: [why]
Date: YYYY-MM-DD
To unarchive: move the row back to Tier 2 in _MANIFEST.md.
Gotchas
- Archive is a manifest move, not a file deletion. The file stays on disk. Don't
rmit. Don't move it to anarchive/folder unless the user explicitly asks. That breaks existing wikilinks. - Tier 3 entries still need wikilinks. Use
[[filename]]in the Tier 3 row so the Obsidian graph keeps the node connected. - Don't strip the closets entry. The file's
_CLOSETS.mdentry stays, withstatus: archived. Future searches still surface it, just at lower priority. - Tier 1 files don't archive.
status.md,decisions.md,glossary.md, etc. are always-loaded by design. Refuse and explain. - Reason is load-bearing. Examples: "wrapped", "superseded by
[[new-file]]", "stale". Future you reads this when deciding whether to unarchive. "no longer needed" is not a reason.
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.
- 4d ago First seen · 64 lines · 57 tokens per session scan A 19aac9dd608f
archive is a skill published in the GitHub repository Skyfox-io/Memex (17 stars, last pushed 2mo ago), licensed MIT. It adds 57 tokens to every session and 718 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
wage-hour-qa
Jurisdiction-aware pay and working time Q&A — NMW/NLW compliance, overtime, rest breaks, holiday pay calculation, final pay, and employment status for pay purposes — answered for the specific jurisdiction with the controlling rule researched and cited rather than stated from memory. Use when the user asks any pay or…
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".