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-best-practicesgit 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-best-practices)<a href="https://agentmods.dev/skills/iamtouchskyer/memex/memex-best-practices"><img src="https://agentmods.dev/badge/skills/iamtouchskyer/memex/memex-best-practices/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-best-practices"><img src="https://agentmods.dev/badge/skills/iamtouchskyer/memex/memex-best-practices.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00021 | $0.02811 |
| Opus 5.5 | $0.00008 | $0.01124 |
| Sonnet 5.5 | $0.00004 | $0.00562 |
| Haiku 4.5 | $0.00002 | $0.00281 |
Grade A, and why
memex-best-practices 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 1mo 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 — 292 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Zettelkasten Best Practices
A reference guide for writing high-quality memex cards that compound in value over time. Covers card format, naming conventions, tagging, linking strategy, and graph health maintenance.
This is NOT a workflow skill (see memex-recall, memex-retro, memex-organize for those). This is a quality standard — consult it when writing or reviewing cards.
Card Quality Checklist
Before writing a card, verify:
- Atomic — one insight per card. If you can split it, do.
- Own words — distill and rephrase, don't copy-paste. This is the Feynman method: if you can't explain it simply, you don't understand it well enough.
- Non-obvious — would this change how you approach a similar task in the future? If not, skip it.
- Linked in context —
[[wikilinks]]are embedded in sentences explaining why the relationship exists.
Card Format
---
title: "Short Noun Phrase ≤60 chars"
created: "YYYY-MM-DD"
source: "<auto-filled by client>"
tags: [domain-tag, type-tag]
category: "<domain>"
---
One atomic insight, written in your own words.
This relates to [[other-card]] because <explanation of the relationship>.
Required Frontmatter
| Field | Required | Format |
|---|---|---|
title |
✅ | Noun phrase, ≤60 chars |
created |
✅ | ISO date YYYY-MM-DD |
source |
✅ | Auto-filled by MCP/CLI client |
Optional Frontmatter
| Field | Format | Notes |
|---|---|---|
tags |
YAML list | See Tag System below |
category |
Single string | See Categories below |
links |
YAML list of slugs | Explicit links (in addition to wikilinks) |
status |
conflict / draft |
Set by organize skill when needed |
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.
- 1mo ago First seen · 292 lines · 21 tokens per session scan A 26acf60e5403
memex-best-practices is a skill published in the GitHub repository iamtouchskyer/memex (144 stars, last pushed 1mo ago), licensed MIT. It adds 21 tokens to every session and 2,811 once invoked, about $0.0001 per session on Opus 5.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
Persist and retrieve agent memory across sessions — recall via the three-stage protocol (structure route → semantic search → navigation fallback), read via memoryload, see the wiki structure via memorybrowse, write well-placed pages via memorywrite (including section-level append/rewrite), maintain via memorycurate.…
memory-dream
Curate the workspace memory wiki as its appointed orchestrator. Trigger on a Cloud-scheduled Dream task or a user's direct curation request. Inspect candidates for orphan leaves, near-duplicates, stale pages, remote conflicts and oversized hubs; browse the graph, cluster leaves into INDEX/hub/leaf structure, maintain…
memory-import
Bulk-import an external knowledge base into Prismer memory via the three-layer import pipeline (07 §3.1). Use when the user asks to import/migrate documents, a knowledge base, or notes into workspace memory. Layer 1 lands raw documents (zero LLM, instantly searchable); Layer 2 is YOUR distillation work — you read the…
prismer-obsidian
Read, search, create, and edit notes in the Obsidian vault.
save-progress
Save current project task progress to local task state file for cross-session continuity. Use when the user asks to save progress, uses an equivalent localized trigger phrase, the session is interrupted, or the user wants to resume work later. Writes to .claude/project-task-state.json so next session can load it via…
memorix
Use when Claude Code needs Memorix shared memory, reasoning, Git Memory, mini-skills, session handoff, orchestration coordination, or integration troubleshooting.