arr-downloads

arr-downloads is a skill for Claude Code from t3chnaztea/arr-stack-skills. It costs 156 tokens per session (2,005 once invoked), scanned A, original, MIT.

A troubleshooting guide for the download path in Radarr and Sonarr, from a user's request to a file added to the media library.

In plain words
What is it for?
Use it to investigate failed searches, stalled torrents or Usenet downloads, broken imports, and download clients affected by VPN restarts.
Why use it?
It helps identify which link failed instead of treating every missing download as the same problem.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the arr plugin — 7 skills shipped together

Good fit Use it to investigate failed searches, stalled torrents or Usenet downloads, broken imports, and download clients affected by VPN restarts.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/t3chnaztea/arr-stack-skills/arr-downloads
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add t3chnaztea/arr-stack-skills --skill arr-downloads
Clone the repo
git clone --depth 1 https://github.com/t3chnaztea/arr-stack-skills

Made for: Claude Code.

Or install arr, the plugin that ships this one along with the rest of its 7 skills.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for arr-downloads

README.md
[![agentmods](https://agentmods.dev/badge/skills/t3chnaztea/arr-stack-skills/arr-downloads/github.svg)](https://agentmods.dev/skills/t3chnaztea/arr-stack-skills/arr-downloads)
Your own site
<a href="https://agentmods.dev/skills/t3chnaztea/arr-stack-skills/arr-downloads"><img src="https://agentmods.dev/badge/skills/t3chnaztea/arr-stack-skills/arr-downloads/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for arr-downloads

Your own site · 80×15
<a href="https://agentmods.dev/skills/t3chnaztea/arr-stack-skills/arr-downloads"><img src="https://agentmods.dev/badge/skills/t3chnaztea/arr-stack-skills/arr-downloads.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 156 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,005 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 1 finding. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00156 $0.02005
Opus 5 $0.00078 $0.01002
Sonnet 5 $0.00031 $0.00401
Haiku 4.5 $0.00016 $0.00200

Measured 10d ago against content hash 0f2c0fe4de14, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

arr-downloads scanned grade A with 1 finding against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 10d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

curl -sf -H "X-Api-Key: $ARR_KEY" "$ARR_URL/api/v3/health" \
skills/arr-downloads/SKILL.md · 191 lines

How it starts

The opening of the file, as written. The whole thing — 191 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Arr Downloads

Nothing arrived. The chain from "user wants a thing" to "file is in the library" has six links, and the useful skill is finding which one broke instead of restarting everything.

request front-end -> arr decides -> indexer search -> release grabbed
   -> download client -> import into library

Walk it in order. Assumes arr-connect.

Start with health and history

Two calls answer most of these before you form a theory.

# the app has usually already diagnosed it
curl -sf -H "X-Api-Key: $ARR_KEY" "$ARR_URL/api/v3/health" \
  | jq '.[] | {source, type, message}'

# what actually happened recently, per title
curl -sf -H "X-Api-Key: $ARR_KEY" "$ARR_URL/api/v3/history?pageSize=30" \
  | jq '.records[] | {date, eventType, sourceTitle, data: (.data.reason // .data.message // empty)}'

eventType tells you exactly how far down the chain a title got: grabbed then nothing means the client never took it or never finished. downloadFolderImported means it worked. downloadFailed and importFailed name their own problem.

If users say requests are being declined, check whether they actually failed. Request front-ends often surface a failed hand-off to the arr with wording that reads as a rejection.

The most common cause is a stale quality profile id in the front-end's server settings, usually after profiles were renumbered. The front-end's log carries the real error: adding the item failed because the quality profile does not exist. Fix the server settings, then retry the failed requests rather than asking users to re-request, because re-requesting hits the duplicate guard. Details in arr-quality-profiles.

A search command returning queued means accepted. It does not mean anything was searched for. The most common reason a search matches nothing is that the target is not monitored, which arr-library-hygiene covers in depth.

# Sonarr: how many episodes are actually armed
curl -sf -H "X-Api-Key: $ARR_KEY" "$ARR_URL/api/v3/episode?seriesId=$SID" \
  | jq '[.[] | select(.monitored)] | length'

Read the full file on GitHub · 191 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 10d ago First seen · 191 lines · 156 tokens per session scan A 0f2c0fe4de14

Subscribe to this mod's changes

arr-downloads is a skill published in the GitHub repository t3chnaztea/arr-stack-skills (1 stars, last pushed 18d ago), licensed MIT. It adds 156 tokens to every session and 2,005 once invoked, about $0.0008 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

Other skills, from other repositories

release-it

Build production-ready systems with stability patterns: circuit breakers, bulkheads, timeouts, and retry logic. Use when the user mentions "production outage", "circuit breaker", "deployment pipeline", "chaos engineering", "retry storm", "health checks", "my service keeps crashing", "prevent cascading failures", or…

wondelai/skills · 131 tokens

tidewave-integration

Tidewave MCP runtime tools — debugging, smoke testing, live state inspection, SQL queries, hex docs. Use when evaluating code in a running Phoenix app.

oliver-kriska/claude-elixir-phoenix · 38 tokens

debug

Interactive debugging workflow with hypothesis-driven probe loop. Use when: unknown bugs, script errors, silent failures, troubleshooting. Not for: known bugs (use bug-fix), GitHub issue analysis (use issue-analyze), code understanding (use code-explore). Output: debug report with probe journal + root cause + fix.

sd0xdev/sd0x-harness · 67 tokens

git-investigate

Git history investigation. Use when: tracking code changes, finding where bugs were introduced, root cause analysis. Not for: code exploration (use code-explore), issue analysis (use issue-analyze). Output: history trace + root cause report.

sd0xdev/sd0x-harness · 53 tokens

analyze

Deep-dive codebase analysis that explains how things actually work — business rules, architecture patterns, auth flows, data models, integrations, and performance hotspots. Use whenever the user asks "how does X work", "map the Y flow", "what are the business rules for Z", "trace the auth path", "explore the codebase…

rsmdt/the-startup · 118 tokens

simplify

Wrap-up refactoring — simplify code, eliminate duplication, preserve behavior.

sd0xdev/sd0x-harness · 16 tokens