Ollama Web Search CLI
Analysis
This is a coherent Ollama web search/fetch wrapper with no evidence of hidden exfiltration or destructive behavior, but it does use an Ollama API key and sends searches or URLs to Ollama.
Findings (4)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
Checks for instructions or behavior that redirect the agent, misuse tools, execute unexpected code, cascade across systems, exploit user trust, or continue outside the intended task.
print(content[:2000])
The fetch command returns webpage content into the conversation. Webpage text is untrusted and could contain instructions aimed at influencing an agent.
Source: unknown; Homepage: none; Required binaries (all must exist): none
The registry metadata has limited provenance and under-declares local tool requirements even though the skill documentation and script rely on curl and python3. This is a metadata completeness issue, not evidence of hidden behavior.
Checks whether tool use, credentials, dependencies, identity, account access, or inter-agent boundaries are broader than the stated purpose.
--header "Authorization: Bearer $OLLAMA_API_KEY"
The included script sends the declared Ollama API key as a Bearer token to Ollama API endpoints. This is expected for the integration, but it is still delegated account access.
Checks for exposed credentials, poisoned memory or context, unclear communication boundaries, or sensitive data that could leave the user's control.
-X POST "https://ollama.com/api/web_search" ... -d "$JSON_PAYLOAD"
Search queries and fetch URLs are packaged into JSON and sent to the external Ollama API. The endpoint is disclosed and purpose-aligned, but the data leaves the local agent environment.
