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/initnpx skills add Skyfox-io/Memex --skill initgit clone --depth 1 https://github.com/Skyfox-io/MemexWhat 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.00053 | $0.01181 |
| Opus 5 | $0.00026 | $0.00590 |
| Sonnet 5 | $0.00011 | $0.00236 |
| Haiku 4.5 | $0.00005 | $0.00118 |
Grade A, and why
init 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 2d 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 — 91 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Memex - Init
Wikilink rule: When referencing any file in markdown you write or edit, always use [[filename]] wikilink format. Never plain text.
Core principle: never assume, never delete. Existing files are sacred. Moves only happen with explicit confirmation.
Step 1: Detect workspace state
Run WORKSPACE_ROOT=$(pwd) && echo "$WORKSPACE_ROOT" via Bash.
| State | Detection | Action |
|---|---|---|
| Empty | No markdown files, no manifest | Quick Start (below) |
| Files, no manifest | Markdown exists, no _MANIFEST.md |
See references/scan-and-organize.md |
| Compatible manifest | _MANIFEST.md exists, no <!-- memex-managed marker |
Offer to add marker (opt in) or continue compatible |
| Old version | <!-- memex-managed:X.X.X --> behind current |
Tell the user to run /memex:upgrade (one-command migration to current version). Init does not perform the migration itself — see references/migrations.md for what changes. |
| Current version | Current marker | See references/health-check.md |
Do not announce the detected state. Just run the appropriate flow.
Quick Start (empty workspace)
- Ask: "What are you working on right now?". Seeds
status.mdwith active focus, in-progress items, next priorities. - Create from
templates/:memory/status.md,memory/session-log.md,memory/decisions.md,memory/glossary.md,memory/_CLOSETS.md(usememory-closets.md.tmpl),scratch/ideas.md. - Append the three Memex lines to workspace-root
CLAUDE.md(template attemplates/CLAUDE.md.tmpl). Preserve existing content. Skip if.claude/CLAUDE.mdalready has them. - Create
_MANIFEST.mdfromtemplates/_MANIFEST.md.tmpl. Tier 1 table, empty Tier 2/3, empty Hub Map. Write last. It's the activation marker. - Print the post-setup message in
references/post-setup-message.md.
Scan and Organize (existing files)
See references/scan-and-organize.md for the full scan / analyze / propose / build flow. Closets file format is canonical at memex/skills/session-end/references/closets-format.md; per-entry summary fields follow memex/skills/session-end/references/summary-rules.md.
What ships with it
15 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.
- references/health-check.md 1.0 KB
- references/migrations.md 1.1 KB
- references/post-setup-message.md 1.1 KB
- references/scan-and-organize.md 4.5 KB
- templates/_MANIFEST.md.tmpl 1.4 KB
- templates/CLAUDE.md.tmpl 534 B
- templates/closets.md.tmpl 303 B
- templates/decisions.md.tmpl 211 B
- templates/domain-index.md.tmpl 135 B
- templates/glossary.md.tmpl 85 B
- templates/ideas.md.tmpl 179 B
- templates/memory-closets.md.tmpl 297 B
- templates/scratch-index.md.tmpl 586 B
- templates/session-log.md.tmpl 311 B
- templates/status.md.tmpl 269 B
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.
- 2d ago First seen · 91 lines · 53 tokens per session scan A 497e94d82535
init is a skill published in the GitHub repository Skyfox-io/Memex (17 stars, last pushed 1mo ago), licensed MIT. It adds 53 tokens to every session and 1,181 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
obsidian
Comprehensive guidelines for Obsidian.md plugin development including ESLint rules from eslint-plugin-obsidianmd v0.4.1, TypeScript best practices, memory management, API usage (requestUrl vs fetch), UI/UX standards, popout window compatibility, community.obsidian.md submission process, and Scorecard optimization. Use…
paid-ads
When the user wants help with paid advertising campaigns on Google Ads, Meta (Facebook/Instagram), LinkedIn, or other ad platforms. Also trigger on "PPC", "paid media", "ROAS", "CPA", "ad campaign", "retargeting", "audience targeting", "Google Ads setup", "Facebook Ads strategy", "LinkedIn Ads". Covers campaign…
sales-enablement
When the user wants to create sales collateral, pitch decks, one-pagers, objection handling docs, or demo scripts. Also trigger on "sales deck", "pitch deck", "one-pager", "leave-behind", "objection handling", "ROI calculator", "demo script", "talk track", "sales playbook", "proposal template". For competitor battle…
aia-generation
Run an AI impact assessment — structured intake, risk analysis, UK regulatory classification (UK GDPR / DPA 2018, ICO AI guidance, sector-specific UK regulation), EU AI Act analysis where EU nexus exists, policy consistency diff, and recommendation with conditions. Uses the house-style structure learned from the seed…
cold-start-interview
Run the cold-start interview — learns your UK AI governance practice and writes /.claude/plugins/config/uk-legal-plugins/ai-governance-legal-uk/CLAUDE.md from your AI policy, a reference impact assessment, and key vendor AI agreements. Use when the practice profile is missing or contains [PLACEHOLDER] markers, or when…
integration-management
Post-completion M&A integration tracker — phased workplan, consent tracking, contract assignment at scale, weekly status reports. Initialises from whatever deal artefacts are available (purchase agreement, deal summary, closing checklist) and connects to deal-context.md and closing-checklist.yaml from the M&A…