Kagi

PassAudited by ClawScan on May 1, 2026.

Overview

This appears to be a straightforward Kagi search/FastGPT wrapper, but users should know it sends queries to Kagi using a local API token and the registry metadata does not fully declare that credential use.

This skill looks safe for its stated purpose if you are comfortable sending searches and prompts to Kagi. Before installing, be aware that it needs a Kagi API token even though the registry requirements do not declare one, and avoid using it for confidential queries unless that fits your Kagi account and privacy expectations.

Findings (3)

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.

What this means

Using the skill can consume Kagi API quota and associate submitted searches or FastGPT prompts with the user's Kagi API token.

Why it was flagged

The skill reads a Kagi API credential from the environment and uses it in the Authorization header. This is expected for a Kagi API wrapper, but it gives the skill delegated access to the user's Kagi API account.

Skill content
tok = os.environ.get("KAGI_API_TOKEN") or os.environ.get("KAGI_API_KEY") ... "Authorization": f"Bot {_token()}"
Recommendation

Use a Kagi API token intended for this purpose, set it only in sessions where the skill is needed, and avoid submitting secrets or highly sensitive content as queries.

What this means

Queries and prompts entered through the skill are shared with Kagi for search or summarization.

Why it was flagged

Search queries and FastGPT prompts are sent to Kagi's external API. This is clearly aligned with the skill's purpose and no unrelated endpoints are shown.

Skill content
BASE_URL = "https://kagi.com/api/v0" ... return _request("POST", "/fastgpt", json_body=body)
Recommendation

Treat search and FastGPT prompts as data sent to a third-party provider, and avoid including passwords, private keys, or confidential material.

What this means

Users have less external provenance information for verifying the origin or maintenance of the skill.

Why it was flagged

The registry metadata does not provide a source repository or homepage. The included code is visible and there is no install script, so this is a provenance note rather than a behavior concern.

Skill content
Source: unknown
Homepage: none
Recommendation

Review the bundled scripts before use and prefer a skill release with a clear source repository or publisher information when available.