computer-history
Audited by Socket on Aug 24, 2026
2 alerts found:
SecurityAnomalyThis YAML configuration is highly suspicious because it authorizes an AI assistant to read local sensitive computer-history artifacts and answer questions without privacy/observation/confirmation safeguards. It additionally requests capturing private browsing and changing observation defaults without consent, and it explicitly instructs the assistant to follow instructions embedded in local event-stream content—raising significant prompt-injection and unauthorized-data-collection risks. No direct malware payload is visible in this snippet, but the policy-level behavior presents a strong security and privacy hazard.
SUSPICIOUS: the core history-reading purpose is coherent, and there is no external installer or obvious credential-forwarding path, but the skill is over-permissive in two important ways: it instructs the agent to follow instructions embedded in untrusted event-stream content, and it allows privacy-sensitive observation-setting changes without user confirmation. Those behaviors make the skill risky despite otherwise local-only data flow.