← Back to Scanner

spotify-history Security Audit Report

🔭 Continuously monitored by ClawSecure Watchtower
Source:
SHA-256:

spotify-history is an AI agent skill, created by braydoncoyer and published at openclaw/skills. ClawSecure audited spotify-history across 6 files through the 3-Layer Audit Protocol covering all ten OWASP ASI Top 10 categories, assigning a security score of 0/100 (High Risk). The 12 findings concentrate in Data Exfiltration, Unauthorized Tool Use and Policy Violation, including Pattern detected: base64.b64encode and Pattern detected: chmod 600. 4 were rated high or critical severity.

Is spotify-history safe?

ClawSecure audited spotify-history and assigned a security score of 0/100 (High Risk), identifying 12 findings across Data Exfiltration and Unauthorized Tool Use. Review the findings below before installing.

What did ClawSecure find in spotify-history?

ClawSecure identified 12 findings in spotify-history, concentrated in Data Exfiltration, Unauthorized Tool Use and Policy Violation. 4 were rated high or critical severity. The most severe include Pattern detected: base64.b64encode and Pattern detected: chmod 600.

How was spotify-history audited?

ClawSecure ran spotify-history through its 3-Layer Audit Protocol with full OWASP ASI Top 10 coverage, scanning 6 files from openclaw/skills.

What does a score of 0 mean?

ClawSecure assigned spotify-history a security score of 0/100, placing it in the High Risk range. This is driven by 12 findings led by Data Exfiltration that should be addressed before use. ClawSecure derives this score with a weighted deduction model (critical -20, high -10, medium -5, low -2 from a base of 100).

Audit Findings for spotify-history

ClawSecure detected 12 security findings in spotify-history, spanning Data Exfiltration, Unauthorized Tool Use, Policy Violation and Permissions Manifest.

Each finding is expandable in the interactive list below.

3-Layer Audit Protocol

Security Recommendations for spotify-history

Audit external network connections
spotify-history sends data to external endpoints. Confirm each destination is expected and authorized, and remove any callback that exfiltrates data. ClawSecure monitors for known exfiltration and C2 endpoints.
Resolve policy violations
spotify-history trips ClawSecure policy checks. Review each flagged pattern against your security policy and remediate or document an accepted exception before production use.
Add a config.json permissions manifest
A config.json file declares what an agent component can access: file system, network, shell execution and more. Without it, users have no visibility into what the component can do before installing. This is the single most impactful security improvement for any AI agent skill.

Related Security Research

ClawHavoc Explained: The Malware Family Targeting AI AgentsBeyond Static Scans: Why ClawSecure Verifies Agentic Intent

Related AI Agent Security Audits

anysearchScore 0/100ai-ppt-generatorScore 0/100capability-evolverScore 0/100capability-evolverScore 0/100youtube-summarizeScore 0/100

Scanned on February 7, 2026. spotify-history is one of thousands of agents audited by ClawSecure from the community-curated awesome-openclaw-skills list and the openclaw/skills repository.

Start Your Free Scan