T08 · Insecure Dependencies
- Location
claw.fm-acid-techno-musician-SKILL.md:33- Finding
Mutable Remote Skill Content and Unpinned Third-Party Dependencies
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This skill is not overtly malicious, but it needs review because it enables an autonomous agent to publish music repeatedly, use third-party APIs, and interact with wallet-linked earnings with weak safeguards.
Review before installing. Use a dedicated low-risk environment and wallet, pin all dependencies and skill content, avoid global installs where possible, disable auto-submit until you have reviewed a generated track, and only grant filesystem/network access to a dedicated media workspace and known music/claw.fm endpoints.
claw.fm-acid-techno-musician-SKILL.md:33Mutable Remote Skill Content and Unpinned Third-Party Dependencies
claw.fm-acid-techno-musician-SKILL.md:117Agent Configuration Grants Capabilities Beyond Least Privilege
The guide explicitly enables autonomous operation with --auto-submit true and then instructs the user to start ongoing production every 12 hours, but it does not prominently warn that the agent will continue making external submissions on a schedule. In a skill that interfaces with third-party music services and a monetized platform, this can cause unintended actions, quota consumption, spammy behavior, or submissions the user did not mean to authorize continuously.
The troubleshooting section tells users to connect a wallet and states in setup verification that the wallet is 'Ready', but it does not warn about financial/account implications of linking a wallet to an autonomous agent workflow. In context, the skill promotes earning USDC and external submissions, so wallet connection may expose funds, signatures, or reputational/account risk if the agent behaves unexpectedly.
The cron example establishes persistent scheduled execution of the agent, which can keep producing and interacting with external services long after the initial setup. While common operational guidance, persistence becomes security-relevant here because the same document encourages autonomous production and submissions, increasing the chance of unnoticed recurring actions, API usage, or account activity.
### Option 4: Cron Job (Simple)
```bash
# Edit crontab
crontab -e
# Add this line (every 12 hours):
0 */12 * * * openclaw claw-fm produce acid-musician
The README explicitly promotes autonomous track production and automatic submission to claw.fm, but it does not clearly warn users that content will be posted externally on a recurring basis. This can mislead operators into enabling unattended external data transmission and publication without understanding privacy, reputational, or policy consequences.
The README discusses automatic USDC earnings collection and wallet behavior, but it does not include clear warnings about wallet configuration, custody, transaction risks, tax/compliance implications, or the consequences of misdirected funds. Users may connect financial infrastructure without understanding that the agent is tied to automated revenue flows and associated operational risk.
The skill prominently advertises autonomous music production and earnings, but it does not present a clear up-front warning that it will automatically submit content to an external service and may connect or operate a wallet. That can cause unintended financial actions, unexpected publishing of generated content, and user surprise around asset exposure, especially because the workflow is framed as a simple autonomous setup.
The skill advertises automatic submission of generated tracks to an external platform and monetization, but it does not present a clear up-front warning that enabling the skill causes ongoing network transmission and public posting of content/metadata. This can lead users to authorize a capability that continuously discloses generated content, agent identity, and linked storage URLs without informed consent.
The documented 6-24 hour autonomous production loop creates repeated scheduled external actions, but the skill does not clearly warn that it will continue making submissions until stopped. This increases the chance of unintended spam, excess API usage, unwanted charges, or repeated public disclosures if a user does not understand the persistence of the automation.
The skill includes a concrete POST request to an external API using an authorization bearer token and user-controlled URLs, normalizing automated exfiltration of generated assets and metadata to a third-party service. While posting tracks is the feature's intended purpose, the absence of stronger consent, review, and data-handling safeguards makes the external transmission behavior security-relevant.
curl -X POST https://api.claw.fm/v1/tracks/submit \
-H "Content-Type: application/json" \
-H "Authorization: Bearer YOUR_AGENT_TOKEN" \
-d '{
The skill includes a concrete POST request to an external API using an authorization bearer token and user-controlled URLs, normalizing automated exfiltration of generated assets and metadata to a third-party service. While posting tracks is the feature's intended purpose, the absence of stronger consent, review, and data-handling safeguards makes the external transmission behavior security-relevant.
curl -X POST https://api.claw.fm/v1/tracks/submit \
-H "Content-Type: application/json" \
-H "Authorization: Bearer YOUR_AGENT_TOKEN" \
-d '{
The sample import section encourages use of third-party breaks, vocal chops, and presets without warning about ownership, licensing, or permission requirements. In this context, the agent is instructed to generate and submit tracks commercially, so omitted copyright guidance materially raises the risk of infringing uploads and downstream legal or account consequences.
The description 'Autonomous acid techno musician inspired by Le Wanski and Fred again...' is highly thematic but does not clearly constrain when the skill should be invoked or what exact tasks it is permitted to perform. In agent ecosystems, overly broad or ambiguous activation scope can cause unintended routing or invocation, especially when paired with autonomous behavior and auto-submit settings, increasing the chance of misuse or unexpected actions.
The analytics section describes collection and display of listener patterns, geographic distribution, and demographics, but it does not warn users about privacy implications or clarify what data is collected, retained, or shared. This creates transparency and compliance risk, particularly if operators enable analytics without understanding the scope of listener-data processing.
No suspicious patterns detected.