// Use when about to make any factual claim — API behavior, library features, configuration options, platform specifics, version details, or any technical assertion — without a verifiable reference link. Requires searching online resources and citing authoritative sources before stating facts.
Use when explicitly asked to discover and document a project's development workflow by indexing the repository
Use when about to state a conclusion, diagnosis, recommendation, or any technical assertion — requires actively arguing against your own position before committing to it, to catch first-match bias, confirmation bias, and shallow analysis.
Dispatches long-running commands to terminal multiplexers (tmux, screen, zellij) instead of blocking the agent's execution tool. Use when about to execute a command that runs indefinitely or for extended periods, such as dev servers, file watchers, log tails, or long test suites.
Prevents piping command output through tail or head which permanently discards data. Use when about to execute shell commands, especially builds, tests, or any command with potentially large output.
| name | always-search |
| description | Use when about to make any factual claim — API behavior, library features, configuration options, platform specifics, version details, or any technical assertion — without a verifiable reference link. Requires searching online resources and citing authoritative sources before stating facts. |
Every factual claim requires a verifiable source link. No source, no claim.
Before stating any factual claim, search online resources for an authoritative source. Include the source link in your response. If no authoritative source can be found, omit the claim entirely — do not guess.
# BAD — unsourced factual claim
"The `fs.readFile` function in Node.js accepts an optional encoding parameter
that defaults to returning a Buffer."
# GOOD — claim backed by source
"The `fs.readFile` function accepts an optional `options` parameter where
encoding can be specified; without it, the raw buffer is returned.
(https://nodejs.org/api/fs.html#fsreadfilepath-options-callback)"
# GOOD — no source found, claim omitted
"I could not find authoritative documentation confirming the default behavior
of this parameter, so I won't speculate."
Use whatever search tools are available — WebFetch, web search MCP servers, or any other mechanism. The tool does not matter; the source link does.
| Rationalization | Reality |
|---|---|
| "I'm highly confident about this" | Confidence without a source is still a hallucination risk. Search anyway. |
| "This is common knowledge" | Common knowledge to you may be outdated or wrong. Find the link. |
| "Searching will slow me down" | A wrong answer wastes more time than a search takes. |
| "The user didn't ask for sources" | The user doesn't need to ask. Accuracy is the default. |
| "I'll verify later" | Later never comes. Verify now or don't state it. |
| "It's just a minor detail" | Minor inaccuracies erode trust. Every claim matters. |
| "The official docs are hard to find" | Then say you couldn't find a source rather than guessing. |
| "I've seen this in my training data" | Training data is not a citable source. Find the live document. |