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 idea-lineagegit 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/idea-lineage)<a href="https://agentmods.dev/skills/timurgaleev/memex/idea-lineage"><img src="https://agentmods.dev/badge/skills/timurgaleev/memex/idea-lineage.svg" alt="Measured on agentmods" height="20"></a>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.00060 | $0.01999 |
| Opus 5 | $0.00030 | $0.01000 |
| Sonnet 5 | $0.00012 | $0.00400 |
| Haiku 4.5 | $0.00006 | $0.00200 |
Grade A, and why
idea-lineage 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 8d 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.
This is a copy
94% identical to idea-lineage — 34 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 223 lines — stays where its author put it; the contents beside it link to each section on GitHub.
idea-lineage - Single-Idea Evolution Through the Brain
Convention: see
conventions/quality.md(viaget_skill conventions/quality) for citation rules, quote fidelity, and source-backed claims.Boundary: takes and facts are different layers — holder-attributed takes (beliefs, bets, hunches by a named holder) versus the brain owner's own hot facts. Do not collapse those layers when summarizing lineage.
What this solves
Users often want to understand how one idea changed across time: when it first appeared, when it became sharp, what it displaced, what it contradicted, and what version is alive now. That is different from building a whole concept map and different from charting an entity's metric trajectory.
Use this skill when the user asks about one idea, topic, phrase, or concept page and wants its evolution through the brain.
Canonical examples:
- "Run idea lineage on founder-led sales."
- "How has my thinking about compounding trust changed?"
- "What is my current version of this idea?"
- "Where did this idea come from, and what did I abandon along the way?"
What this is not
- Not
concept-synthesis: that skill deduplicates many concept stubs, tiers them, writes concept pages, and builds a broad intellectual map. - Not
find_trajectory: that operation charts typed facts or event rows for an entity, such as MRR, role, location, or status over time. - Not a contradiction-probe runner: this skill may read cached contradiction findings when available, but it does not launch expensive probes.
- Not a writing mode by default: do not write a lineage page unless the user explicitly asks for a saved artifact after seeing the read-only answer.
Contract
This skill guarantees:
- A single-idea scope is preserved. Broad corpus or "map my concepts" prompts
route to
skills/concept-synthesisinstead. - Every lineage claim cites existing brain evidence: page slug, source id when present, date, and short quote or snippet.
- Missing evidence is labeled as a gap, not patched with plausible narrative.
- Contradictions, reversals, and abandoned branches are separated from normal temporal evolution.
- The default mode is read-only and does not mutate brain pages.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 8d ago First seen · 223 lines · 60 tokens per session scan A 0f6d5a0e231a
idea-lineage is a skill published in the GitHub repository timurgaleev/memex (8 stars, last pushed today), licensed MIT. It adds 60 tokens to every session and 1,999 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 94% identical to idea-lineage, differing in 34 lines, and is treated as a copy.
Other skills, from other repositories
kb
Set up, evolve, or operate a hraness/kb local-first Markdown knowledge base for coding-agent memory. Use when a user asks to design KB conventions or a recurring KB ritual; search or query a KB or Obsidian vault; load or recover repository context, plans, decisions, concepts, backlinks, semantic search, or Git…
grounded-knowledge-workflow
Use Grounded Knowledge Engine to select an isolated workspace, answer from local evidence, resume an explicitly identified project, create an explicit project checkpoint, and retain durable knowledge. Trigger when a user asks about their documents, workspace or client context, previous research, project state…
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.
gbrain-ingest
Ingest meetings, articles, docs, and conversations into the brain. Updates existing pages with new info, creates pages for new entities, maintains cross-references.
gbrain-query
Answer questions from the brain using FTS5 + semantic search + structured queries. Synthesizes across multiple pages with citations.
gbrain-maintain
Periodic brain maintenance. Finds contradictions, stale info, orphan pages, and missing cross-references to keep the knowledge graph healthy.