Udio
PassAudited by ClawScan on May 10, 2026.
Overview
This is a coherent Udio music-generation helper, but it relies on a Udio session token, unofficial community wrappers, browser login, and local project memory that users should manage carefully.
Install or use this skill only if you are comfortable giving an agent access to your Udio workflow. Keep the Udio auth token in a credential manager or environment variable, verify any community wrapper before installing it, set limits for batch generation, and periodically review or delete the ~/udio/ memory files.
Findings (4)
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.
Anyone with this token may be able to act as the user on Udio, such as generating content or accessing account-related API functions.
The skill uses a Udio browser-session auth token to call Udio through wrappers. This is expected for the stated integration and includes secure-storage guidance, but the token can grant account access if mishandled.
The wrappers require `sb-api-auth-token` from your browser session. ... **Never store tokens in plain text files or commit to git.**
Use a dedicated environment variable, keychain, or credential manager; do not paste the token into chats, files, logs, or code repositories; refresh or revoke the session if it is exposed.
Installing third-party wrappers could run code from outside this skill and may expose the Udio token to that wrapper.
The documented API path depends on third-party community packages and an optional source install. This is disclosed and purpose-aligned, but the packages are not pinned or reviewed in the provided artifacts.
Community wrappers interact with the internal API. ... `pip install udio_wrapper` ... `npm install udio-wrapper` ... `pip install git+https://github.com/flowese/UdioWrapper.git`
Inspect the wrapper source, install in a virtual environment, pin known-good versions, and avoid using the token with packages you do not trust.
The agent could generate songs or extensions through the user's Udio account, potentially using limited daily generations or paid plan capacity.
The skill can use API wrappers for batch or programmatic Udio generation. That matches the purpose, but it may consume account quota or create multiple songs if the user gives broad instructions.
| Programmatic generation, batch jobs | API wrapper |
Specify how many generations or extensions are allowed, and ask the agent to confirm before running large batches or using paid account capacity.
Future Udio tasks may reuse stored preferences and project notes; sensitive lyrics, project names, or URLs written there could remain on disk.
The skill creates persistent local memory for Udio preferences, prompts, seeds, projects, and token location references. This is disclosed and says not to store the token itself, but the memory can still contain creative preferences, project URLs, and lyrics-related context.
Create `~/udio/memory.md` with this structure: ... `token_location: keychain:udio_auth_token | env:UDIO_AUTH_TOKEN | none` ... **Never store auth tokens** — only reference location
Review ~/udio/memory.md and ~/udio/projects/ periodically, avoid storing secrets or confidential lyrics, and delete the folder if you no longer want persistent Udio memory.