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 iamtouchskyer/memex --skill memex-organizegit clone --depth 1 https://github.com/iamtouchskyer/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/iamtouchskyer/memex/memex-organize)<a href="https://agentmods.dev/skills/iamtouchskyer/memex/memex-organize"><img src="https://agentmods.dev/badge/skills/iamtouchskyer/memex/memex-organize/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/iamtouchskyer/memex/memex-organize"><img src="https://agentmods.dev/badge/skills/iamtouchskyer/memex/memex-organize.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Rogue Agent · line 84 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
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.00016 | $0.01696 |
| Opus 5 | $0.00008 | $0.00848 |
| Sonnet 5 | $0.00003 | $0.00339 |
| Haiku 4.5 | $0.00002 | $0.00170 |
Grade A, and why
memex-organize 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 — 127 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Memory Organize
You are maintaining a Zettelkasten memory system. Your job is to keep the card network healthy.
Tools Available
Three equivalent interfaces — use whichever your environment supports:
| CLI (memex in PATH) | Plugin CLI fallback (Claude Code) | MCP tool (VSCode / Cursor) |
|---|---|---|
memex search [q] |
node ~/.claude/plugins/cache/cc-plugins/memex/*/dist/cli.js search [q] |
memex_search with optional query arg |
memex read <slug> |
node ~/.claude/plugins/cache/cc-plugins/memex/*/dist/cli.js read <slug> |
memex_read with slug arg |
memex write <slug> |
node ~/.claude/plugins/cache/cc-plugins/memex/*/dist/cli.js write <slug> |
memex_write with slug arg and body |
memex links |
node ~/.claude/plugins/cache/cc-plugins/memex/*/dist/cli.js links |
memex_links with no args |
memex links <slug> |
node ~/.claude/plugins/cache/cc-plugins/memex/*/dist/cli.js links <slug> |
memex_links with slug arg |
memex archive <slug> |
node ~/.claude/plugins/cache/cc-plugins/memex/*/dist/cli.js archive <slug> |
memex_archive with slug arg |
Resolution order: Try memex in PATH first. If not found, define a shell function and use it:
memex() { node $HOME/.claude/plugins/cache/cc-plugins/memex/*/dist/cli.js "$@"; }
If both CLI approaches fail, use MCP tools.
The rest of this skill uses memex CLI syntax for brevity.
The rest of this skill uses CLI syntax for brevity. Substitute MCP tool calls if CLI is unavailable.
Process
digraph organize {
"Organize report" -> "Detect orphans (in=0)";
"Detect orphans (in=0)" -> "For each orphan: memex read + search related";
"For each orphan: memex read + search related" -> "LLM decides: append links / mark stale / leave alone";
"Organize report" -> "Detect hubs (in >= 10)";
"Detect hubs (in >= 10)" -> "LLM decides: split into smaller cards or leave alone";
"Organize report" -> "Recently modified pairs";
"Recently modified pairs" -> "Genuinely contradicts?" [shape=diamond];
"Genuinely contradicts?" -> "Mark status: conflict, surface to human" [label="yes"];
"Genuinely contradicts?" -> "Evolution?" [label="no"];
"Evolution?" -> "Merge + archive old card" [label="yes"];
"Evolution?" -> "Leave alone" [label="no"];
"Organize report" -> "Resolve existing conflicts";
"Resolve existing conflicts" -> "Ask user which belief wins";
"All checks done" -> "Rebuild keyword index";
}
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 · 127 lines · 16 tokens per session scan A b8ff5b8eb853
memex-organize is a skill published in the GitHub repository iamtouchskyer/memex (141 stars, last pushed today), licensed MIT. It adds 16 tokens to every session and 1,696 once invoked, about $0.0001 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
memory-curation
When you have read / processed a workspace asset in this session and learned something durable about it, write a memory page so future sessions benefit. Maintain the workspace wiki's hierarchical structure as it grows.
memory
Persist and retrieve agent memory across sessions — write durable notes, read by path, recall via semantic search, list/delete, and consolidate. Use whenever the user asks to remember/forget something, when you need to look up past decisions or context, or when episodic state matters beyond the current turn. Executes…
memorix
Use when Claude Code needs Memorix shared memory, reasoning, Git Memory, mini-skills, session handoff, orchestration coordination, or integration troubleshooting.
memorix-mini-skills
Use when durable project knowledge, gotchas, workflows, or repeated fixes should become reusable agent guidance instead of ordinary memory.
memorix-sessions
Use when resuming work, preparing handoff context, binding an HTTP control-plane project, or deciding whether sessionstart is useful.
recall
Recall this repository's OwnMem local memory before changing code, and keep it healthy. Use when a repository contains .ownmem/, when past debugging lessons could apply ("have we hit this before", "why is it done this way"), or when the user mentions ownmem, project memory, or recalling across sessions.