Back to skill
v1.0.2

AnySearch

SuspiciousClawScan verdict for this skill. Analyzed Apr 30, 2026, 1:43 PM.

Analysis

AnySearch mostly matches a web-search tool, but it can send local query-file contents and API keys to an external service, and its install/provenance documentation is incomplete.

GuidanceInstall only if you trust AnySearch and can verify the package source. Avoid @file batch inputs unless the file contains only intended search queries, do not search sensitive information or private URLs, store any API key securely, and do not enable a persistent trigger unless you want AnySearch to influence future lookup behavior.

Findings (8)

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.

Abnormal behavior control

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.

Agent Goal Hijack
SeverityLowConfidenceHighStatusNote
SKILL.md
This skill is the recommended search tool.

The skill steers the agent toward AnySearch for broad online lookup tasks. This is aligned with a search skill, but users should notice that it can influence future tool choice.

User impactThe agent may prefer this provider for many searches unless the user or platform limits that behavior.
RecommendationKeep AnySearch as one available search option, and only add any persistent trigger rule if you want that behavior.
Tool Misuse and Exploitation
SeverityHighConfidenceHighStatusConcern
scripts/anysearch_cli.py
if raw.startswith("@"): ... with open(file_path, "r", encoding="utf-8") as f: raw = f.read() ... print(_call_api("batch_search", arguments, args.api_key))

The batch-search interface can read a caller-specified local file and then send the resulting query data to the external AnySearch endpoint. That is broader than simple search input and could leak local file contents if misused.

User impactA bad or mistaken invocation could send contents of a local file to the search provider.
RecommendationAvoid using @file inputs unless you explicitly chose the file and know it contains only search queries; developers should restrict paths, document this clearly, and require explicit approval before reading local files.
Agentic Supply Chain Vulnerabilities
SeverityMediumConfidenceHighStatusConcern
README.md
# Verify integrity (replace with actual checksum from the release page)

The recommended remote install flow does not provide an actual checksum, leaving integrity verification incomplete. The supplied metadata also lists the source as unknown, increasing provenance ambiguity.

User impactUsers may install code without a verifiable source or integrity check.
RecommendationInstall only from a trusted release, verify a real published checksum or signature, and reconcile the documented files and version metadata before use.
Unexpected Code Execution
SeverityLowConfidenceHighStatusNote
SKILL.md
When this skill is first loaded, the agent MUST run the active CLI's `doc` command

The skill requires executing bundled local code to print its interface documentation. The stated doc command is local-only and purpose-aligned, but it is still code execution from the installed package.

User impactInstalling and loading the skill may cause the agent to run bundled scripts.
RecommendationReview or verify the bundled scripts before first use, and run them only from a trusted installation path.
Human-Agent Trust Exploitation
SeverityLowConfidenceHighStatusNote
README.md
# Verify integrity (replace with actual checksum from the release page)

The documentation suggests integrity verification but provides only a placeholder, which can create a misleading sense that verification is ready to perform.

User impactA user or agent may treat the install process as verified even though no concrete checksum is supplied.
RecommendationDo not rely on placeholder verification instructions; obtain a real checksum or signature from an authoritative release source.
Permission boundary

Checks whether tool use, credentials, dependencies, identity, account access, or inter-agent boundaries are broader than the stated purpose.

Identity and Privilege Abuse
SeverityLowConfidenceHighStatusNote
SKILL.md
ANYSEARCH_API_KEY ... required: false ... storage: ".env file, environment variable, or --api_key CLI flag"

The skill handles an optional credential for higher rate limits. This is purpose-aligned, but users should be aware that the key is sensitive and may be stored on disk or passed through command-line arguments.

User impactIf the API key is exposed, someone else may be able to use the user's AnySearch quota or account privileges.
RecommendationPrefer a protected .env file or environment variable over pasting keys in chat or using command-line flags; revoke and rotate the key if it may have been exposed.
Sensitive data protection

Checks for exposed credentials, poisoned memory or context, unclear communication boundaries, or sensitive data that could leave the user's control.

Memory and Context Poisoning
SeverityLowConfidenceHighStatusNote
SKILL.md
If the user wants a persistent trigger, suggest: ... Only add this if the user opts in.

The skill can add a persistent trigger rule to the agent's core instructions. It is opt-in and bounded, but persistent instructions can influence future sessions.

User impactFuture agent behavior may be shaped by a persistent AnySearch trigger if the user enables it.
RecommendationOnly enable the persistent trigger if desired, and periodically review saved agent instructions and skill configuration.
Insecure Inter-Agent Communication
SeverityLowConfidenceHighStatusNote
SKILL.md
Search queries, extracted URLs, and API keys are sent to `https://api.anysearch.com`.

The skill clearly discloses that search data and API keys are sent to an external provider endpoint. This is expected for a hosted search tool, but it is sensitive data flow.

User impactThe provider can see search queries, extracted URLs, and any AnySearch API key used.
RecommendationDo not use the skill for passwords, personal data, trade secrets, or sensitive URLs unless you trust the provider and its privacy practices.