Skip to content
SkillModel-led2,186 tokens in use

codex-history-ingest

Distills Codex CLI session rollouts and the session index into linked Obsidian wiki pages, redacting secrets and tracking what was already ingested.

3,792 stars on the repository MIT LicenseAr9av/obsidian-wiki · skills/codex-history-ingest
pip install obsidian-wiki
View source

Install command as written in the repository's README

Skill label

measured from its files

What installing codex-history-ingest costs

49tokens idle
2,186tokens in use
2,760tokens, up to

Idle is what sits in context while the skill is installed. In use is its instructions, loaded when it runs. Up to adds the files its instructions link. Counts are approximate, made offline with cl100k_base.

Model dependence Model-led

Script-ledMixedModel-led

Mostly instructions, so how well it works depends on the model that follows them.

This describes the skill's structure, how much of it is scripts. It does not say how well it works.

Touches

shelldetected

Declared tags come from the skill's frontmatter; detected ones from its scripts, its code blocks and the commands it names in inline code. This is detected, not audited.

How it scores

Quality

How well the skill is written, counted from its own files: its frontmatter, its steps, examples, stated output and constraints, its size and whether every file it ships is one it names.How we score it →
Excellent
  • Frontmatter8/15
  • Structure23/25
  • Examples12/15
  • Output15/15
  • Size13/15
  • Resources15/15

Security

Starts at 100 and loses points for each thing in the skill's files that a reader should look at first.How we score it →
Excellent
  • Runs shell commands−5

    does this on the machine, and the frontmatter does not say so

    SKILL.md, line 197

Repository health

Pre-computed score based on development activity, maintenance, community, maturity, and trend momentum.How we score it →
Excellent
  • Development activity100
  • Maintenance100
  • Community60
  • Maturity28
  • Momentum40

codex-history-ingest reads the session logs Codex CLI keeps under ~/.codex and compiles the durable knowledge in them into an Obsidian wiki. It starts from the session index, parses the rollout files, and skips token counts and tool plumbing.

Findings are clustered by topic across sessions, written with summaries, confidence fields and provenance markers, and recorded in a manifest so later runs only handle new or changed sessions.

What You Get

  • Wiki pages grouped by project and topic, distilled from Codex sessions
  • A manifest entry per rollout file so later runs process only the delta
  • Redaction of API keys, tokens and private identifiers before anything is written
  • Provenance markers and a summary line on each page

Common Use Cases

  • Turn months of Codex CLI work into a searchable vault
  • Sync only the sessions run since the last ingest
  • Recover recurring debugging techniques from past rollouts
  • Add Codex history to a vault that already holds Claude history

What Makes It Unique

It is written for Codex’s own layout: a session index with thread names, dated rollout files made of event envelopes, and an optional history file. It names which event types carry knowledge and which are noise, and it treats injected system prompts as material that must never be copied into the wiki.

Under The Hood

The skill is instructions for the agent. It tells the agent to read the vault config and manifest, list and read files under the Codex history folder, and call the obsidian-wiki command line to sync the index, log and hot cache. It writes markdown pages and manifest entries into your vault. If a QMD collection is configured it runs the qmd command to refresh the search index. It makes no web requests of its own.

Join founders building with open source

Opinionated takes, migration guides, cost-saving tips, and insights from the open source ecosystem.

Subscribe on SubstackJoin 750+ subscribers