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 skills add ondrejmirtes/mcparr --skill interactive-release-searchgit clone --depth 1 https://github.com/ondrejmirtes/mcparrWrote 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/ondrejmirtes/mcparr/interactive-release-search)<a href="https://agentmods.dev/skills/ondrejmirtes/mcparr/interactive-release-search"><img src="https://agentmods.dev/badge/skills/ondrejmirtes/mcparr/interactive-release-search/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.
<a href="https://agentmods.dev/skills/ondrejmirtes/mcparr/interactive-release-search"><img src="https://agentmods.dev/badge/skills/ondrejmirtes/mcparr/interactive-release-search.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00146 | $0.00607 |
| Opus 5.5 | $0.00058 | $0.00243 |
| Sonnet 5.5 | $0.00029 | $0.00121 |
| Haiku 4.5 | $0.00015 | $0.00061 |
Grade A, and why
interactive-release-search scanned grade A with 0 findings 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 1mo 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.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
Choosing a release
Releases are returned sorted by seeders descending. Seeders matter (more = faster and more reliable), but they are not the only factor. See references/release-scoring.md for details.
Quick rules
- Never grab
rejected: true. Therejectionsarray says why (wrong quality, too large, already imported, release-group banned…). Report it instead. - Match the expected quality. If the user (or the show's quality profile) expects
1080p, don't grab a 2160p REMUX that's 60 GB — or a 480p cam. The
qualityfield tells you what each release is. - Among acceptable releases, prefer more seeders. Torrents with 0–1 seeders may
never complete; a release with 50 seeders at slightly lower
customFormatScoreis usually the better real-world choice. - Size sanity check. Wildly small files for the resolution are fake/spam; wildly
large ones may blow the user's disk. Use
sizeGBand common sense per quality. - Prefer higher
customFormatScorewhen two releases are otherwise equivalent — it reflects the user's configured preferences (codecs, groups, language). - Usenet vs torrent. Usenet releases have
seeders: nulland sink to the bottom of the seeder sort; they can still be excellent (no peers needed). Don't dismiss a usenet release just because it has no seeders.
When to ask vs. act
- One clearly-best approved release at the expected quality → grab it, then report.
- Multiple plausible choices (e.g. 1080p vs 2160p, or several groups) → present the top 2–3 with quality/size/seeders and let the user choose.
- Only rejected releases → don't grab; explain the rejection reasons.
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.
- 1mo ago First seen · 47 lines · 146 tokens per session scan A 1e09746533e7
interactive-release-search is a skill published in the GitHub repository ondrejmirtes/mcparr (6 stars, last pushed 4mo ago), licensed MIT. It adds 146 tokens to every session and 607 once invoked, about $0.0006 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
overseerr
Search, request, and manage media through Overseerr (movies/TV shows via Radarr/Sonarr). Use when someone asks to find, request, or check the status of a movie or TV show on your Plex server.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
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…