Security audit
Security checks for vulnerabilities and agentic risk
This skill is a straightforward Sonarr helper, but users should be careful because some documented commands can change the media library, trigger downloads, or delete media-related records.
Install only if you intend to let the agent use your Sonarr API key. Review prompts carefully before allowing add, delete, blacklist, rename, rescan, or missing-episode search actions, because they can modify your media library, trigger downloads, or affect files managed by Sonarr.
Remote code is downloaded and executed. This bypasses code review and could introduce malicious code.
# 1. Look up by title (returns TVDB results)
curl -s "$SONARR_URL/api/v3/series/lookup?term=Breaking+Bad" \
-H "X-Api-Key: $SONARR_KEY" | python3 -c "
import sys,json
results = json.load(sys.stdin)
Remote code is downloaded and executed. This bypasses code review and could introduce malicious code.
"
# 2. Get quality profiles and root folders
curl -s "$SONARR_URL/api/v3/qualityprofile" -H "X-Api-Key: $SONARR_KEY"
curl -s "$SONARR_URL/api/v3/rootfolder" -H "X-Api-Key: $SONARR_KEY"
# 3. Add the series
Remote code is downloaded and executed. This bypasses code review and could introduce malicious code.
curl -s -X POST "$SONARR_URL/api/v3/command" \
-H "X-Api-Key: $SONARR_KEY" \
-H "Content-Type: application/json" \
-d '{"name":"MissingEpisodeSearch"}'
The documentation includes DELETE operations for episode files and queue items, including blacklisting, but does not warn users that these actions can remove files or alter download behavior. For markdown files, destructive or system-affecting behavior should be explicitly disclosed to avoid unintended data loss or workflow disruption.
The skill documents state-changing Sonarr operations such as adding series and triggering missing-episode searches without any warning, confirmation step, or constraint on when these actions are appropriate. In an agent setting, this increases the chance of unintended library modification, download activity, and downstream interaction with indexers/download clients from a casual or ambiguous prompt.
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
"
# 2. Get quality profiles and root folders
curl -s "$SONARR_URL/api/v3/qualityprofile" -H "X-Api-Key: $SONARR_KEY"
curl -s "$SONARR_URL/api/v3/rootfolder" -H "X-Api-Key: $SONARR_KEY"
# 3. Add the series
This POST command instructs Sonarr to perform a MissingEpisodeSearch, which can initiate downstream automated searches and downloads via integrated services. In a skill context, exposing this action as a simple example without warning or confirmation makes unintended triggering materially more likely.
curl -s -X POST "$SONARR_URL/api/v3/command" \
-H "X-Api-Key: $SONARR_KEY" \
-H "Content-Type: application/json" \
-d '{"name":"MissingEpisodeSearch"}'
This markdown file documents state-changing operations including adding, updating, and deleting series, but it provides no warning that these actions modify or remove user-managed media records. Under the markdown-file criteria, descriptions should disclose behaviors that could affect user data or system state.
The Commands section documents operational actions such as searching, rescanning folders, refreshing metadata, and renaming files, all of which can materially affect the user's library or external services. The markdown does not include any warning about these side effects, despite the potential impact on user data, disk state, or connected systems.
No suspicious patterns detected.