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 reindexgit 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/reindex)<a href="https://agentmods.dev/skills/skyfox-io/memex/reindex"><img src="https://agentmods.dev/badge/skills/skyfox-io/memex/reindex/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/skyfox-io/memex/reindex"><img src="https://agentmods.dev/badge/skills/skyfox-io/memex/reindex.svg" alt="Reviewed on agentmods" width="80" 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.00058 | $0.01953 |
| Opus 5 | $0.00029 | $0.00977 |
| Sonnet 5 | $0.00012 | $0.00391 |
| Haiku 4.5 | $0.00006 | $0.00195 |
Grade A, and why
reindex 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 9d 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 — 164 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Memex - Reindex
Wikilink rule: When referencing any file in markdown, always use [[filename]] wikilink format.
Walk every Tier 2 hub in _MANIFEST.md and (re)generate _CLOSETS.md for each. Session-end refreshes touched hubs incrementally; reindex covers the long tail in one pass.
Picking the right migration tool:
/memex:resummarize. Rewrites manifest + hub summaries to v2 format./memex:reindex. Rebuilds the per-hub closets index used for retrieval.
Run resummarize for summary format upgrades, reindex for closets coverage. They're independent; on a fresh v1→v2 migration, run resummarize first, then reindex.
Step 0: Detect workspace, acquire lock, parse arguments
Run WORKSPACE_ROOT=$(pwd) && echo "$WORKSPACE_ROOT" via Bash. Read _MANIFEST.md:
- Missing or no
<!-- memex-managedmarker: Tell the user "Memex isn't initialized here. Run/memex:initfirst." and stop.
Acquire memory/.reindex.lock and check the 24-hour cooldown in memory/.reindex-runs.log. Both follow the shared bulk-write convention. See ../consolidate/references/locking.md.
Parse $ARGUMENTS:
--hub <name>. Limit to one hub (e.g.,--hub fundraising). Useful for spot rebuilds.--force. Rebuild every entry from scratch, ignoring mtime checks. Also bypasses the 24-hour cooldown.
Step 1: Build the hub list
Read _MANIFEST.md. For each row in the Hub Map, parse the wikilink in the Hub column:
- Legacy form
[[<domain>-index]]. Hub folder = parent of the index file. Closets file:<hub-folder>/_CLOSETS.md. - Closets-only form
[[<domain>/_CLOSETS]](v2.1+). Hub folder = the parent folder of the closets file. No index file expected.
Resolve absolute paths for each hub folder and its closets / archive. Archive (if any): <hub-folder>/_CLOSETS-archive.md.
Also include memory/ as a synthetic hub. Its closets file is memory/_CLOSETS.md; its files are the Tier 1 files listed in _MANIFEST.md (status, session-log, decisions, glossary, plus any user-added Tier 1 entries). The memory hub has no archive (Tier 1 is a small fixed set, not paginated).
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.
- 9d ago First seen · 164 lines · 58 tokens per session scan A b6e6f201d641
reindex 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 1,953 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
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…