Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/timurgaleev/memexnpx agentmods add skills/timurgaleev/memex/captureWrote 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/timurgaleev/memex/capture)<a href="https://agentmods.dev/skills/timurgaleev/memex/capture"><img src="https://agentmods.dev/badge/skills/timurgaleev/memex/capture/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/timurgaleev/memex/capture"><img src="https://agentmods.dev/badge/skills/timurgaleev/memex/capture.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 3 findings, 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 Agent Snooping · line 106 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
- medium Agent Snooping · line 107 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
- medium Agent Snooping · line 108 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
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.00041 | $0.01179 |
| Opus 5.5 | $0.00016 | $0.00472 |
| Sonnet 5.5 | $0.00008 | $0.00236 |
| Haiku 4.5 | $0.00004 | $0.00118 |
Grade A, and why
capture 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 — 112 lines — stays where its author put it; the contents beside it link to each section on GitHub.
capture — the single ingestion entrypoint
When the user wants to save a thought, an article snippet, a transcript
fragment, or any text into their brain, run memex capture. Don't reach
for a raw page_put from the shell — capture is the front door and it
handles slugging, frontmatter, and the receipt for you.
Contract
- Input: the content to save (inline arg,
--file PATH, or--stdin). - Output: a page in the brain DB. The brain is DB-canonical — the page IS the artifact; there is no companion file on disk. Receipt printed to stdout.
- Side effect: the page becomes immediately queryable via
query,search, or any MCP-bound agent. - Idempotency: same content → same
inbox/YYYY-MM-DD-<hash8>slug. Content-hash dedup catches re-captures. - Trust: all captures via this skill are local-CLI trust. Untrusted remote ingestion goes through the public MCP ingress with its own redaction and write-allowlist, not this verb.
When to invoke
- "Capture this thought" / "save this" / "drop this into my brain" / "remember this"
- The user pastes content and asks to keep it
- After a meeting summary, a research note, or any synthesis that should land as a brain page
What it does
memex capture resolves to a page_put call against the brain. The page
lands in the DB in one move and is indexed for retrieval. The default slug
is inbox/YYYY-MM-DD-<hash8> so captures cluster in a predictable triage
location. From an MCP client (no shell), the equivalent is a direct
page_put with an inbox/ slug and the same frontmatter stamps.
How to use
memex capture "the thought I want to remember"
memex capture --file ./notes/today.md
echo "from a pipe" | memex capture --stdin
memex capture "..." --slug daily/2026-05-21
memex capture "..." --type idea --source voice-whisper
memex capture "..." --quiet # script-friendly: prints just the slug
memex capture "..." --json # structured output for agents
Defaults
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 · 112 lines · 41 tokens per session scan A 8965497f2972
capture is a skill published in the GitHub repository timurgaleev/memex (11 stars, last pushed 21d ago), licensed MIT. It adds 41 tokens to every session and 1,179 once invoked, about $0.0002 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-31.
Other skills, from other repositories
memory
Use this skill when Pioneer should proactively use durable memory or recalled context: decide whether memory can improve a turn, answer from remembered user/project facts, request memory tools, search/list/get stored memories, save durable preferences or project decisions, forget memories, audit or clean up memory, or…
thebrain-ingest
Lay material into TheBrain as a connected graph rather than a pile of notes. Use when asked to "put this article in my brain", "save this", "add it to the knowledge base", "break this down and record it" — about an article, a document, a discussion, a research result or the user's own thinking. Covers: how finely to…
thebrain-organize
Tidy up TheBrain: find duplicates, thoughts with no links, empty stubs, scattered branches about the same thing. Use when asked to "clean up my brain", "find duplicates", "what is dangling with no links", "sort this out", "the structure has drifted". Covers: how to hunt for disorder, what you may fix yourself, and…
thebrain-digest
Report what happened in the brain over a period, and what deserves going back to. Use when asked "what did I add this week", "show me a digest", "what have I been working on", "what is new in the brain", and at the start of a session when the context of previous work needs recalling. Covers: how to read the…
weasley-deepmind
A reference for using weasley-deepmind, a server that stores and retrieves an AI agent’s long-term memories between sessions. It describes memory storage, search, language processing, and related tools.
thebrain-research
Use TheBrain as a knowledge base when answering a question: look at what is already known first, and only then reason. Use when asked "what do I know about X", "what do I have on this topic", "have we discussed this already", "remind me what we concluded", and before any substantive answer on a topic that might be in…