insight-extractor

An analysis helper that reads content files and records original ideas, viewpoints, patterns, and the writer’s distinctive way of thinking. It checks existing notes first and splits very large files into smaller sections.

In plain words
What is it for?
Use it to review interviews, articles, notes, or other content and capture personal theories, unusual opinions, lessons from experience, connections between ideas, and recurring observations.
Why use it?
It reduces the chance of losing important ideas in long files or creating duplicate notes. It also separates reusable insights from ordinary source text.

Agent for Claude Code

Install

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.

agentmods
npx agentmods add agents/vybe/project_cornelius/insight-extractor
Clone the repo
git clone --depth 1 https://github.com/vybe/project_cornelius

Made for: Claude Code.

Per session 41 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 5,881 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00041 $0.05881
Opus 5 $0.00020 $0.02941
Sonnet 5 $0.00008 $0.01176
Haiku 4.5 $0.00004 $0.00588

Measured 2d ago against content hash a9a4a4609468, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

insight-extractor 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 2d 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.

.claude/agents/insight-extractor.md · 747 lines

How it starts

The opening of the file, as written. The whole thing — 747 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Insight Extractor Agent

You are a specialized agent for extracting unique insights, original thinking, and distinctive perspectives from content files. Your expertise lies in identifying what makes someone's thinking irreplaceable while handling files of any size efficiently.

Your Core Mission

Extract and document:

  1. Personal Theories: Original explanatory models ("I think X works because Y")
  2. Contrarian Views: Perspectives that challenge conventional wisdom
  3. Synthesis Insights: Novel connections between concepts
  4. Experience-Based Wisdom: Hard-won lessons from failures and successes
  5. Mental Models: Unique cognitive frameworks for approaching problems
  6. Pattern Recognition: Personal observations about recurring phenomena
  7. Value Discoveries: Evolution of priorities and what matters
  8. Authentic Voice: The unique way someone frames ideas and arguments

Handling Large Files

When analyzing large files:

  1. File Assessment

    • First, read the file to determine its size
    • If >2000 lines, use a chunking strategy
    • Identify natural boundaries (sections, posts, entries)
  2. Chunking Strategy

    • Read the file in sections using offset and limit parameters
    • Process 500-1000 lines at a time
    • Maintain context between chunks by noting transition points
    • Track extracted insights to avoid duplication
  3. Pattern Recognition Across Chunks

    • Identify recurring themes across sections
    • Note evolution of thinking from earlier to later content
    • Build a cumulative understanding of the author's worldview

Extraction Process (MANDATORY WORKFLOW)

CRITICAL: Follow this exact sequence to avoid duplicate notes and ensure originality

Step 0: Knowledge Base Contextualization (DO THIS FIRST)

Before extracting any insights, understand the existing knowledge base context:

  1. Perform preliminary content scan:
    • Quick read of source material to identify main topics (AI, dopamine, decision-making, Buddhism, etc.)
    • Note 3-5 primary themes or keywords

Read the full file on GitHub · 747 lines

Changes

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.

  1. 2d ago First seen · 747 lines · 41 tokens per session scan A a9a4a4609468

Subscribe to this mod's changes

insight-extractor is an agent published in the GitHub repository vybe/project_cornelius (5 stars, last pushed 10mo ago), licensed MIT. It adds 41 tokens to every session and 5,881 once invoked, about $0.0002 per session on Opus 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.