The fastest useful agent is usually not the biggest one. Wrap the tools you already trust, preload only the context the job needs, and keep broad agents out of small repeated tasks.
Start With The Tool
Build the agent around one CLI, API, repo, or repeatable workflow. A narrow helper should have a clear job before it gets a clever personality.
Preload The Right Context
Static prompt context works for stable jobs. Dynamic context works when the helper needs to load files, docs, API data, or a project-specific bundle before answering.
This is about as instant as I've ever seen an AI respond to anything, because it just has that context preloaded in.
— John Lindquist
Keep The Agent Narrow
If the task needs web research, product judgment, or multi-system reasoning, send it back to a general agent or a heavier planning workflow. The narrow agent should stay boring, quick, and predictable.
I don't want them to reason or think about things. I want them to know exact file paths, exact examples, and then maybe some basic file editing, but not too much more than that.
— John Lindquist
Prefer Tools With CLIs Or APIs
Command-line and API surfaces give the agent something concrete to inspect, execute, and verify. They also make it easier to turn a vague repeat task into a small wrapper with reliable inputs and outputs.
Treat Account Permissions As Setup
OAuth screens, account state, credential storage, scopes, and admin permissions are setup concerns. They should be checked deliberately and kept out of shared examples unless they are sanitized and current.
Make Self-Improvement Reviewable
Store suggested changes, inspect them, and apply them deliberately. A self-improving helper is only useful if its changes are reviewable and reversible.
Prove Generated Helpers
A newly generated imp is draft tooling until the source, link/install behavior, and smoke tests check out. Do not share the generated helper as a setup path until it can answer one harmless query and show the command evidence.