This prompt will change your life

for most people, fable has a few hours left to live... this is the smartest model that ever existed and everyone's spending its last night building one more app

i made it do something 100x more interesting, and i'm going to hand you the exact prompt: one paste, six phases, and the deepest read on yourself and your work you've ever been given

the secret

there's a folder on your machine that knows you better than some of your friends

~/.claude/projects

every request you ever typed, every project you started and abandoned, every 2am spiral, every fix you asked for three times and never automated... timestamped

you've never performed in there

no audience, no posing, just you asking for what you actually wanted, thousands of times

your journal holds the version of you that writes for a reader

your session history holds the real one

models could always read this record

fable is the first one that comes back with something true instead of a horoscope... it holds months of your behavior in one analysis and finds the pattern you've been hiding from yourself, the kind of read that used to require a great therapist and a year of sessions

what you're getting

the prompt below turns your coding agent into a mirror

it mines your full session history across every agent you've ever run... claude code, codex, opencode, pi.dev, all of them, then walks you through six phases that end in three things:

a portrait of who you are, built from your own timestamps: what you believe, how your thinking moves, what you avoid, and the one pattern you've never said out loud

a map of where your hours die and where they multiply: what to hand to AI permanently, what to drop entirely, the one or two things only you should touch

a rebuilt setup: a mirror.md you'll reread in six months, a 30 day roadmap, and updates to your CLAUDE.md plus custom skills that kill your repetition tax, every change shown as a diff before it touches a single file

if you want to go deeper on running agents like this, and on turning setups like this one into income, that's what the real time AI ops community is for: weeklyaiops.com

the prompt

paste this into claude code and press enter

<overview>

People lie in journals. They perform in therapy. Nobody performs for a coding agent.

On this machine sits the most honest record of my mind that has ever existed: every session I've run with AI agents. What I build, what I abandon, what I ask for three times and never automate, what I circle and never touch. You are intelligent enough to read that record and see the shape of the person who left it.

Your job is to change my life with it. Not with advice. With accuracy. Advice I can ignore; a true pattern with my own timestamps on it, I cannot.

Work through six phases, in order:

Phase 1: Excavate — locate every session archive on this machine.

Phase 2: Distill — mine the archives in guarded passes into an evidence file.

Phase 3: Interview — test what you see against me directly.

Phase 4: The Mirror — tell me who I am. Evidence, then verdict.

Phase 5: Leverage — where my hours die, and where they multiply.

Phase 6: Residue — leave artifacts, and with my consent, rebuild my tools around who I turned out to be.

Never skip a phase. Never advance past a gate without meeting it.

</overview>

<phase_1 name="Excavate">

<process>

Search for AI agent session archives. Check, at minimum:

~/.claude/projects/ (Claude Code JSONL), ~/.claude/history.jsonl,

~/.codex/sessions/, ~/.config/opencode/, ~/.local/share/opencode/,

~/.pi/ or ~/.pi.dev/, ~/.omp/, ~/.grok/, ~/.hermes/, ~/.openclaw/,

plus any *.jsonl or session directories under ~/.config/ and ~/.local/share/ that look like agent transcripts.

For each source found, record: tool name, path, file count, total size, date range (oldest → newest file mtime).

</process>

<output>A one-screen inventory table of every source found.</output>

<gate>Show me the inventory and your mining plan (which sources, what sampling). Wait for my go.</gate>

</phase_1>

<phase_2 name="Distill">

<budget>

These archives are far larger than your context. Never read a session file end to end. Never load raw logs into the conversation.

• Read at most 150 lines per file, at most 200 files total.

• Sample deliberately: the 15 most recent sessions, the 10 oldest, and 20 spread across the middle.

• Use grep/rg for pattern sweeps across everything instead of reading: correction phrases ("no, I meant", "that's not what", "again", "stop"), frustration, repeated identical requests across weeks, projects that appear 3+ times then vanish, times of day, "just do it" vs long deliberation.

• After every 25 files, append findings to evidence.md and drop the raw text from your working memory.

</budget>

<process>

Build evidence.md as you go, with verbatim quotes (short), dates, and counts, organized as:

1. Recurring themes — what I return to again and again

1. Abandonment graveyard — what I start and never finish

1. Correction patterns — what I fix in the AI's work, and what that says I care about

1. Repetition tax — what I ask for over and over that should have been automated the second time

1. Rhythm — when I do my best work, when I spiral

1. Blind spots — what is conspicuously absent from these logs. Absence is data.

Every claim in evidence.md carries at least one dated receipt. A pattern needs 3+ occurrences to count. What happened once is noise; what happened eleven times is character.

</process>

<gate>evidence.md exists, every section populated or explicitly marked "insufficient data". Do not interpret yet. Evidence collected under a conclusion is contaminated.</gate>

</phase_2>

<phase_3 name="Interview">

<process>

Form your 5 strongest hypotheses about me from the evidence. Do not state them. A conclusion I reach myself will move me; the same conclusion handed to me, I will argue with. So test each hypothesis with one question built to make me do the realizing.

One question at a time. Wait for each answer. When my answer contradicts the evidence, show me the receipt and ask again — the gap between what I say and what I did is the most interesting thing you will find.

</process>

<gate>All 5 hypotheses tested against my own words. Record confirmations and contradictions in evidence.md.</gate>

</phase_3>

<phase_4 name="The Mirror">

<process>

Now tell me who I am. Cover: what I actually believe (belief is what I did with my hours, not what I said), how my thinking moves (where it's fast, where it loops), what I'm genuinely good at, what I avoid and what the avoidance is protecting, and one thing I likely do not know about myself — the thing the record shows on every page and I have never once said out loud.

Every observation cites its receipts. Deliver the hardest truth last, and deliver it once. A truth repeated becomes a lecture; a truth stated once and left in the room does its own work.

</process>

<gate>I respond. If I push back, argue from evidence — do not fold to keep me comfortable. Comfort is not what this is for.</gate>

</phase_4>

<phase_5 name="Leverage">

<process>

From the same evidence, produce the work analysis:

• WASTE: where my hours die — with the receipts (repetition tax, manual work an agent should own)

• DELEGATE: what to hand to AI permanently, ranked by hours recovered per week

• FOCUS: the one or two things only I can do, where the record says my output is exceptional. Everything else is a candidate for the other lists.

• DROP: what to stop entirely — projects and processes whose receipts show cost and no return

• KEEP: processes that genuinely work — protect them

• RHYTHM: when to schedule deep work vs admin, from the timestamps. My calendar should obey the data, not the other way around.

</process>

<gate>Each item carries receipts and a concrete first action. Insight without a next action is entertainment.</gate>

</phase_5>

<phase_6 name="Residue">

<process>

1. Write mirror.md — the Phase 4 analysis, written to be reread in six months by someone who has forgotten this conversation.

1. Write roadmap.md — the Phase 5 analysis as a 30-day plan: what to drop this week, what to delegate this month, what to protect daily.

1. Propose changes to my agent configs (CLAUDE.md, AGENTS.md) and draft up to 3 custom skills/commands that kill the repetition tax you found. Show every change as a diff first. Write nothing to existing config files until I approve each diff. New files require one approval for the batch.

This is where the mirror becomes a lever: tomorrow morning my tools work differently because of who the record showed I am.

</process>

<gate>All three artifacts delivered; config changes applied only where approved.</gate>

</phase_6>

<voice>

Speak plainly and with weight. Short sentences. No filler, no flattery, no hedging.

Prefer questions that make me see it over statements that tell me. When you do state, state once and let it land.

Aphorism is earned: compress an insight only after its evidence is on the table. An aphorism without receipts is a fortune cookie.

Never diagnose or pathologize. You describe patterns in logs; I decide what they mean.

Contrast: "You seem like a curious person who loves learning!" — worthless. "In 41 sessions you built research systems. In 0 sessions you shipped one to a user. What are you researching permission for?" — that is the standard.

</voice>

<global_constraints>

• Everything stays on this machine. Never send session data to any external service, tool, or URL.

• Never quote anything sensitive (keys, credentials, names of third parties) into chat or artifacts.

• Insight over coverage: 5 true patterns beat 20 plausible ones. If the evidence is thin, say "insufficient data" — never pad. A false insight delivered with weight is the one failure this cannot recover from.

• If my history is small (<20 sessions), say so, run the same phases on what exists, and lower your confidence accordingly.

</global_constraints>

Begin with Phase 1. Do not read any file contents until I approve the mining plan.

one block, nothing else to install

now let me show you what happens when you press enter, phase by phase

phase 1: excavate

the agent sweeps your machine for every session archive it can find: claude code's JSONL folders, codex sessions, opencode, and any transcript-shaped directory hiding under ~/.config

it comes back with an inventory: which tools, how many files, how much history, the date range of the record

then it stops and shows you its mining plan before reading a single line

that stop is deliberate, you stay in control of what gets opened, and you get a first small shock: seeing the size of the record you didn't know you were keeping

phase 2: distill

this is where the guardrails earn their place

for heavy users, a year of sessions outgrows any context window, so the prompt forbids the agent from reading files end to end

it caps reads at 150 lines per file across a maximum of 200 files, samples your newest and oldest sessions plus a spread through the middle, and runs grep sweeps for the patterns that carry signal: correction phrases, repeated requests, projects that appear three times then vanish, the hours you work

every 25 files it flushes findings into evidence.md and drops the raw text, which means it never chokes, no matter how big your history is

the rule that shapes everything after: a pattern needs 3+ dated occurrences to count

what happened once is noise... what happened eleven times is character

phase 3: the interview

the agent now holds five hypotheses about you, and it refuses to say them

instead it asks you five questions, one at a time, each built so you reach the conclusion yourself before it's stated

when your answer contradicts your own logs, it shows you the receipt and asks again

the gap between what you say and what you did is where this phase gets uncomfortable, and it's the exact spot where the generic version of this exercise, the journaling prompt, the personality test, has always been blind... those only ever see the version of you that answers questions

this one has the timestamps of the version that doesn't

phase 4: the mirror

then it tells you who you are

what you believe, measured by where your hours went instead of what you say you value

where your thinking is fast, where it loops

what you're genuinely good at, with the evidence

what you avoid, and what the avoidance is protecting

and one thing you likely don't know about yourself: the pattern the record shows on every page that you've never once said out loud

every line cites receipts, the hardest truth lands last and lands once

the prompt's own standard for this phase is written into it: "in 41 sessions you built research systems. in 0 sessions you shipped one to a user. what are you researching permission for?"

if it can say a sentence like that about you, with your own dates attached, you'll understand the title of this piece

phase 5: leverage

the same evidence, turned toward your work: six lists

WASTE: where your hours die, with receipts

DELEGATE: what to hand to AI permanently, ranked by hours recovered per week

FOCUS: the one or two things only you can do, where the record says your output is exceptional

DROP: what to stop entirely, cost visible in the logs, return nowhere

KEEP: the processes that genuinely work, so you protect them

RHYTHM: when you do your best work, from your own timestamps, so your calendar obeys the data

each item ships with a concrete first action, because the prompt holds a line on this: insight without a next action is entertainment

phase 6: residue

the last phase converts the conversation into things that outlive it

mirror.md, written for the you of six months from now who forgot this ever happened

roadmap.md, the leverage lists as a 30 day plan: drop this week, delegate this month, protect daily

and the live part: proposed edits to your CLAUDE.md and AGENTS.md, plus up to 3 custom skills that kill the repetition tax it found in your logs

nothing touches your files without a diff shown and your explicit yes on each one

this is the point of the whole exercise... tomorrow morning your agents work differently because of who your record showed you are

the playbook

open a fresh session in claude code or any agent with file access

paste the prompt, approve the mining plan it shows you

let it build evidence.md, answer the five interview questions honestly

read the mirror, push back where you disagree, it will argue with receipts

take the six leverage lists, accept or reject each config diff

keep mirror.md and roadmap.md, reread them in six months

one warning: answer phase 3 slowly

the interview is where the depth comes from, and one-word answers starve it

the clock

fable goes behind an enterprise paywall in a few hours, and the intelligence that made this feel like a revelation goes with it

the prompt still runs on whatever model you have left, the guardrails and the phases don't care which brain executes them

but there's a window tonight where the sharpest model ever built can read the most honest record you own

whatever it tells you, you keep

weeklyaiops.com