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 timurgaleev/memex --skill ingestgit clone --depth 1 https://github.com/timurgaleev/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/timurgaleev/memex/ingest)<a href="https://agentmods.dev/skills/timurgaleev/memex/ingest"><img src="https://agentmods.dev/badge/skills/timurgaleev/memex/ingest/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/ingest"><img src="https://agentmods.dev/badge/skills/timurgaleev/memex/ingest.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.00017 | $0.02933 |
| Opus 5.5 | $0.00007 | $0.01173 |
| Sonnet 5.5 | $0.00003 | $0.00587 |
| Haiku 4.5 | $0.00002 | $0.00293 |
Grade A, and why
ingest 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 — 298 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ingest Skill
Ingest meetings, articles, media, documents, and conversations into the brain.
Filing rule: Read
skills/_brain-filing-rules.md(viaget_skill _brain-filing-rules) before creating any new page.
Contract
- Every fact written to a brain page carries an inline
[Source: ...]citation with date and provenance. - Every entity mention creates a back-link from the entity's page to the page mentioning them (Iron Law).
- Raw sources are preserved for provenance via the
put_raw_datatool. - State sections are rewritten with current best understanding, never appended to.
- Entity detection fires on every inbound message; notable entities get pages or updates.
Convention: See
conventions/quality.md(viaget_skill conventions/quality) for Iron Law back-linking.
Every mention of a person or company with a brain page MUST create a back-link
FROM that entity's page TO the page mentioning them. An unlinked mention is a
broken brain. See skills/_brain-filing-rules.md for format.
Citation Requirements (MANDATORY)
Every fact written to a brain page must carry an inline [Source: ...] citation.
- User's statements:
[Source: User, {context}, YYYY-MM-DD] - Meeting data:
[Source: Meeting "{title}", YYYY-MM-DD] - Email/message:
[Source: email from {name} re: {subject}, YYYY-MM-DD] - Web content:
[Source: {publication}, {URL}, YYYY-MM-DD] - Social media:
[Source: X/@handle, YYYY-MM-DD](URL)(include link) - Synthesis:
[Source: compiled from {sources}]
Phases
Router note: This skill is a router. For specialized ingestion, see: idea-ingest, media-ingest, meeting-ingestion.
- Parse the source. Extract people, companies, dates, and events from the input.
- For each entity mentioned:
- Read the entity's page with
page_getto check if it exists - If exists: update compiled_truth (rewrite State section with new info, don't append)
- If new: check notability gate, then store the page with
page_putwith the appropriate type and slug
- Read the entity's page with
- Append to timeline. Add a timeline entry with
add_timeline_eventfor each event, with date, summary, and source citation. - Create cross-reference links. Use
linkfor every entity pair mentioned together, with the appropriate relationship type. - Back-link all entities. Update EVERY mentioned entity's page with a back-link to this page (Iron Law).
- Timeline merge. The same event appears on ALL mentioned entities' timelines. If Alice met Bob at Acme Corp, the event goes on Alice's page, Bob's page, and Acme Corp's page.
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 · 298 lines · 17 tokens per session scan A ecab0663c93d
ingest is a skill published in the GitHub repository timurgaleev/memex (11 stars, last pushed 29d ago), licensed MIT. It adds 17 tokens to every session and 2,933 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-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…
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-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…
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…