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.
npx agentmods add skills/trtmn/agent-plugins/jellyfinnpx skills add trtmn/agent-plugins --skill jellyfingit clone --depth 1 https://github.com/trtmn/agent-pluginsWrote 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.
[](https://agentmods.dev/skills/trtmn/agent-plugins/jellyfin)<a href="https://agentmods.dev/skills/trtmn/agent-plugins/jellyfin"><img src="https://agentmods.dev/badge/skills/trtmn/agent-plugins/jellyfin.svg" alt="Measured on agentmods" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00125 | $0.01553 |
| Opus 5 | $0.00063 | $0.00776 |
| Sonnet 5 | $0.00025 | $0.00311 |
| Haiku 4.5 | $0.00013 | $0.00155 |
Grade A, and why
jellyfin 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 3d 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.
description: Interact with a Jellyfin media server via its REST API using the `jellyfin` CLI (a curl wrapper with 1Password auth). Use this skill whenever the user wants to browse or search their Jellyfin library, trigge How it starts
The opening of the file, as written. The whole thing — 132 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Jellyfin API Skill
Interact with a Jellyfin media server through its REST API.
The jellyfin CLI is a thin curl wrapper that injects the API key and server URL
from 1Password, so neither the secret nor the (private) hostname is ever printed,
placed on argv, or committed to git.
Why curl, not restish? Jellyfin's official OpenAPI spec has deeply recursive schemas that crash restish (stack overflow on load), so the spec-driven approach isn't viable. The REST endpoints are simple, so a curl wrapper is both reliable and lightweight. Full endpoint reference: https://api.jellyfin.org/.
CLI — jellyfin
Installed at ~/.local/bin/jellyfin. It resolves the API key (credential) and
server URL (hostname) from one 1Password item via op run, sends the key as the
X-Emby-Token header, and pretty-prints JSON responses with jq.
Shorthands (most common)
jellyfin scan # trigger a full library scan/refresh (POST /Library/Refresh)
jellyfin libraries # list libraries / virtual folders
jellyfin search "the matrix" # search hints across the library
jellyfin search "dune" 5 # ...limited to 5 results
jellyfin sessions # list active playback sessions
jellyfin users # list users
jellyfin system-info # server system info
jellyfin tasks # list scheduled tasks
Raw HTTP
Reach any endpoint in the Jellyfin API directly. A
request body for post/put is the 3rd argument or piped on stdin.
jellyfin get "/Items?searchTerm=blade+runner&limit=5&Recursive=true"
jellyfin get "/Items/<itemId>"
jellyfin get "/System/Info/Public" # unauthenticated server info
jellyfin post "/Sessions/<sessionId>/Playing/Pause" # remote playback control
jellyfin post "/Sessions/<sessionId>/Message" '{"Text":"Dinner!","Header":"Note"}'
jellyfin post "/ScheduledTasks/Running/<taskId>" # run a scheduled task
jellyfin delete "/Items/<itemId>"
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 3d ago First seen · 132 lines · 125 tokens per session scan A b3218362e1f4
jellyfin is a skill published in the GitHub repository trtmn/agent-plugins (2 stars, last pushed 6d ago), licensed Unlicense. It adds 125 tokens to every session and 1,553 once invoked, about $0.0006 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.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…