obsidian-vault

HIGH W007: Insecure credential handling detected in skill instructions.

• Insecure credential handling detected (high risk: 1.00). The prompt embeds a literal Obsidian API key and shows Authorization: Bearer usage in curl examples, meaning an agent generating commands or requests would need to include that secret verbatim (or otherwise expose it) to function—this is high-risk secret handling.

CRITICAL E006: Malicious code pattern detected in skill scripts.

• Malicious code pattern detected (high risk: 0.90). The content includes a plaintext Obsidian Local REST API bearer token plus explicit curl and filesystem commands that directly enable reading, searching, creating, modifying, and deleting all vault files (and thus can be used to exfiltrate or tamper with sensitive data and cloud‑synced content if abused).

HIGH W008: Secret detected in skill content (API keys, tokens, passwords).

• Secret detected (high risk: 1.00). The prompt contains a high-entropy, literal API key shown in clear text:

d4fc944e64f535df05b34c2e8596c4e3eaffc6dfd5b5ee15e76789a4ab96698a

It is labeled "API Key" and shown as the bearer token for the Obsidian Local REST API, which would provide access when used in Authorization headers. This matches the definition of a secret (long, random-looking credential). No other values meet the high-entropy secret criteria (paths, localhost URL, environment variable names, and example commands are not secrets).