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 commands/zelixag/ai-memex-cli/fetchgit clone --depth 1 https://github.com/zelixag/ai-memex-cliWhat 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.00000 | $0.00190 |
| Opus 5 | $0.00000 | $0.00095 |
| Sonnet 5 | $0.00000 | $0.00038 |
| Haiku 4.5 | $0.00000 | $0.00019 |
Grade A, and why
fetch 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.
What it actually says
memex fetch
Fetch web content or documentation into the raw/ directory.
Usage
/memex:fetch <url> [options]
Examples
/memex:fetch https://react.dev/reference/react/hooks/memex:fetch https://docs.anthropic.com --depth 2/memex:fetch https://nextjs.org/sitemap.xml --sitemap
Instructions
Current memex agent: claude-code
When calling a memex CLI command that delegates semantic work to an agent, pass --agent claude-code unless the user already provided an explicit --agent.
Run the following shell command, substituting $ARGS with any arguments
the user provided after /memex:fetch:
memex fetch $ARGS
Report the command output to the user. If the command modifies wiki pages, briefly summarize what changed.
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 · 30 lines · 0 tokens per session scan A 08326a727c44
fetch is a command published in the GitHub repository zelixag/ai-memex-cli (9 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 190 tokens. 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-31.
Other commands, from other repositories
wiki-query
Ask questions against the wiki. Synthesizes answers from wiki pages with cross-reference citations.
wiki-req
Capture and decompose a concept into atomic, traceable wiki requirements. Clarifies ambiguous requirements, splits them into atomic pieces, and persists them as wiki/requirements/ pages with status tracking.
wiki-ingest
Process new source packets and synthesize them into wiki knowledge pages.
wiki-record
Capture the just-completed task's tool-call trajectory into the wiki as agent working-memory, then optionally distill it into a reusable skill.
wiki-retro
Save an atomic insight from the current task into the wiki. Creates a single markdown file that layered recall surfaces in future sessions.
wiki-run
Run the full wiki cycle: discover → ingest → lint. Optionally schedule for auto-updates.