1 · Evaluate a tool
15 minTake the last tool or repository someone recommended to you and run the prompt in the AI that knows your project.
Done when: you have the 4 answers and a verdict, IN or LEFT OUT, noted in the log.
Lesson 4 · 13 min
Every week a new repository shows up promising everything. Handle it with tongs: before installing, ask your AI whether it fits your stack and what you gain. And don't use the same model for everything: each agent can have its own, among the best, the economical and the free.
Start the lesson
Goal: choose each agent's model by cost and task, and test any new tool against your stack before installing it.
Tap each step.
Three tiers. The names change every month; the criteria stay.
Coding, finance and decisions involving money call for the strongest model your plan offers.
The cost of an error here is higher than the price difference.
Customer service, triage and summaries run many times a day. A cheaper, faster model can handle them.
Test with 20 real cases before switching.
There are open, free models with huge context windows, good for prototyping and for tasks with no sensitive data.
Check the provider's data policy: free sometimes means your data trains the model.
For a financial plan, ask two agents running different models for the same analysis, with the same context, and compare.
Where they agree, you gain confidence; where they disagree, that's the question you need to ask.
Run the first one in the AI that already knows your project.
Someone recommended this tool to me: <name and link>. You know my stack (languages, services, what's already running). Answer in up to 10 lines: 1. DOES IT FIT? What language and infrastructure does it run on, and does that work with my stack? 2. DO I ALREADY HAVE IT? What I already use that does the same thing or close to it. 3. WHAT DO I GAIN? One concrete task that would get better, with a number if possible. 4. RISK? Data access, maintenance, license, dependence on third parties. Verdict: IN (<deadline> test on one task) or OUT (reason in 1 line).
DATE | TOOL | VERDICT | REASON <dd/mm> | <name> | out | different language, repeats what the CRM already does <dd/mm> | <name> | in | 2-week test on the purchasing agent
Use a real recommendation you received.
Take the last tool or repository someone recommended to you and run the prompt in the AI that knows your project.
Done when: you have the 4 answers and a verdict, IN or LEFT OUT, noted in the log.
Go back to the orchestra map (lesson 3) and mark each agent's tier: best, economical or free.
Done when: every agent on the map has a tier and the reason in a few words.
The lesson's mechanism explained in about two and a half minutes.
4 questions.
Question 1 of 4
A colleague recommends an excellent repository, but it's all in another language and repeats what your system already does. What do you do?
Question 2 of 4
Which agent deserves the strongest model?
Question 3 of 4
Two agents with the same context disagreed about the cash plan. Is that bad?
Question 4 of 4
A free model has a huge context. What should you watch out for before using it?
Pick an option. The explanation shows up after you try.