Improving GitHub Agent Instructions for Better Module Recognition

Hi Dust team, I've set up an agent with a github data source. I have given instructions to my agent and the end is this: Initial analysis: Before any response, start by analyzing the files or documents present in your knowledge base, if they exist. Clarify the need: Systematically ask the user questions to identify any missing or implicit points in their requirements. The aim is to help the user specify what he really wants, even on aspects he hasn't thought of. Need validation : Once you've obtained the answers, reformulate the need as you've understood it. Explicitly ask the user to validate this reformulation. You don't generate any answers or code until the validation has been confirmed. However, the agent often tells me that he can't find the module I'm talking about, even though it's present in the data source. Should I give him a more precise instruction? Kind regards