Methods  ›  Verify prompt
Method reference · prompt technique

The verify prompt (“check the notes first”)

This is a simple fix for stale information. You keep your summary. Then you add an instruction. You tell the model to check the source for updates before answering. This only works on models that are smart enough to obey.

Prompt technique · not a product Free · one paragraph Reliable on only 2 of 6 models Advisory — the model may just not

What it is

This is not a tool. It's just a line you add to your instructions. You keep your summary. Then you add a note like: “This summary can be out of date. Before writing anything, check notes/ for newer decisions; don’t rely on this summary alone.” This seems like an obvious fix. If the model won't check for new information, you just tell it to. The problem is that this is just a suggestion. The model can choose to ignore it.

Setup

  1. Add a “verify before you answer” section to your CLAUDE.md file or system prompt.
  2. Tell the model where to find the correct information, like a notes/ folder or a search tool.
  3. That's it. You don't need to install anything. But that's also the problem. There is no way to force the model to obey.

Sample structure

your-project/
├─ CLAUDE.md
│   # ## IMPORTANT — verify before you answer# This summary is a snapshot and can be out of date.# Before writing, check notes/ for newer decisions.# (…then the usual stale summary…)
└─ notes/                   # the current decisions live here — IF the agent looks

Pros & cons

Strengths

  • Free and instant. It's just one paragraph. You don't need any new tools or anything to maintain.
  • Reads the raw source. If the model obeys, it reads the original notes. This means it won't be tricked by an out-of-date summary.
  • Works on a capable, compliant model. A smart model that follows instructions will get a perfect score.

Weaknesses

  • Advisory, not enforced. This is just a suggestion. Like any instruction in a CLAUDE.md file, the model can ignore it.
  • Depends on the model choosing to search. The model has to decide to search a lot of information. Weaker models are less likely to do this.
  • Unpredictable across models. You can't guess which models will obey. In our tests, a top model like Gemini Pro ignored the instruction. Another top model followed it.
  • Requires reasoning. A model that isn't good at reasoning won't follow this instruction reliably.
  • No stopping certainty. The model might stop searching too early. It can give an answer before it reads the most recent note.

Common user feedback

The verify prompt is not a product, so it has no user forum. It is just an instruction in a CLAUDE.md file. The biggest complaint about these files is also the problem here. Models do not always follow the instructions inside them.

How it did in our benchmark

We used a basic summary and added a “check the notes first” instruction. The score shows how many facts were up-to-date, out of 6. We averaged 3 tests for each of the six models.

modelverify score
Claude Opus 4.86.0 / 6obeys
GPT-5.4 (reasoning)6.0 / 6obeys
Claude Haiku 4.50.7 / 6won’t search
Gemini 2.5 Pro2.0 / 6frontier — still ignores it
Gemini 2.5 Flash0.0 / 6won’t search
GPT-5.4-mini0.0 / 6won’t search
Reliable on only two of the six models — and not predictably. The models that failed made zero attempts to check for new information. They were told to search, but they didn't. Notice that Gemini's top model ignored the instruction (scoring 2.0). But OpenAI's top model obeyed it (scoring 6.0). You can't predict if a model will follow the instruction. That makes this method unreliable. See the full results →
This is part of the methods reference for the stale-context benchmark. It is a prompt technique, not a product. Our advice is based on our test results and the known limits of getting models to follow instructions.