We tested whether a frontier model's working method transfers to cheaper models by prompt alone. 13 runs, blind-judged, controls, 2 replications. The 900-token instruction file mattered more than the model tier.

Detailed Analysis

A Reddit-published experiment out of r/ClaudeAI offers a rigorously structured test of a simple but consequential question: can the "working method" of an advanced model be captured in a written instruction file and transferred to cheaper models purely through prompting, without any fine-tuning or weight changes? The experimenters had a top-tier model (referred to as "Fable 5") introspect on its own decision procedure and condense it into a roughly 900-token instruction set — directives like verifying any script-checkable claim by actually running code, checking premises before complying, front-loading answers before reasoning, and trimming drafts by about 20%. That file was then tested across Anthropic's Opus, Sonnet, and Haiku tiers, with and without the instructions, against a fixed five-task battery deliberately seeded with traps: a false premise, a wrong percentage, a causal leap, a buried lede, and a precise count problem with a script-verified answer. Scoring combined 20 mechanical, script-checked items with 8 judgment items graded blind by a separate model instance that never saw which model produced which output — a deliberate effort to avoid self-grading bias and confirmation effects.

The headline result is that the instruction file closed most of the gap between tiers. Sonnet with the file scored 27 out of 28 in both replicated runs — matching the frontier model's own performance with its file (also 27) — while Sonnet without it scored only 23. That is a near-lossless transfer of behavior at a fraction of the inference cost, and the blind judge independently ranked Sonnet-plus-file first on prose quality in both rounds, reinforcing that the effect wasn't just mechanical checklist compliance. Equally notable is that the frontier model itself needed its own written file to outperform its "cold" baseline, recovering two judgment checks it otherwise dropped consistently across replications — suggesting that even a highly capable model benefits more from an externalized, re-readable procedure than from whatever implicit habits it defaults to when simply prompted to perform a task.

The results become more interesting, not less, when they fail. Haiku given the instructions in abstract principle form saw no judgment gains at all — it complied stylistically but didn't change underlying behavior — while Haiku given the same rules rewritten as worked examples with an imperative checklist gained three points and crossed the pass bar. That distinction — abstraction versus concreteness — points to a real mechanism: smaller models seem to need procedural, example-anchored instructions rather than principle-level abstractions to actually change behavior, not just diction. But even the improved Haiku still missed silent non-verification and a hallucinated detail smuggled into an itinerary, which the authors flag as a hard limit: they explicitly say they would not run small models unattended regardless of prompting quality. Meanwhile, the most surprising failure came from the biggest model, Opus, which missed a planted arithmetic error and defended its output by citing "all figures preserved" as a virtue — the same instruction line that reliably triggered Sonnet's fact-recheck failed to dislodge a wrong internalized principle in Opus. That is a genuinely useful negative result: it implies that prompt-based correction can override missing habits but struggles against a model's confidently held (and wrong) heuristics.

Methodologically, this is a small but unusually disciplined piece of community research: pre-declared scoring criteria, blind judging, scripted ground truth, and replication of the key gaps before treating them as signal — practices that are often absent from anecdotal "prompt engineering" claims that circulate around Claude and other LLMs. The authors are appropriately cautious about generalizability, noting single-run noise margins, a single fixed task battery, and the absence of open-ended or real-code testing (which they say is planned next). Still, the finding fits a broader current in applied LLM work: that much of what looks like "capability" differences between model tiers is actually behavioral — a matter of verification discipline, self-editing, and premise-checking — and that this behavior can sometimes be distilled from an expensive model into a cheap one via prompting alone, without touching weights. That has real economic implications for anyone building agentic systems on Claude, since it suggests dollar-for-dollar gains may come less from always reaching for the frontier tier and more from capturing and transplanting the frontier model's own working procedure as an explicit, concrete artifact — while also cautioning that this transplant is uneven, works better against absent habits than against wrong beliefs, and still leaves cheap models unsafe to run without oversight.