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 commands/nickperrott/videodrome-plugin/configuregit clone --depth 1 https://github.com/nickperrott/videodrome-pluginWrote 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/commands/nickperrott/videodrome-plugin/configure)<a href="https://agentmods.dev/commands/nickperrott/videodrome-plugin/configure"><img src="https://agentmods.dev/badge/commands/nickperrott/videodrome-plugin/configure.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.00000 | $0.01018 |
| Opus 5 | $0.00000 | $0.00509 |
| Sonnet 5 | $0.00000 | $0.00204 |
| Haiku 4.5 | $0.00000 | $0.00102 |
Grade A, and why
configure 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 4d 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.
How it starts
The opening of the file, as written. The whole thing — 150 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/videodrome:configure
Configure Plex MCP server environment variables interactively.
Usage
/videodrome:configure
Description
This command launches an interactive configuration wizard that helps you set up all required environment variables for the Plex MCP server:
- Plex Server - URL and authentication token
- TMDb API - API key for metadata lookup
- Media Paths - Root directory for your media library
- Optional Features - Auto-ingest and file watching
The wizard will:
- Guide you through each setting with examples
- Validate your inputs
- Test connections to Plex and TMDb
- Save configuration to
.envfile - Backup existing configuration if present
What You Need
Before running this command, gather:
- Plex Server URL - Usually
http://YOUR_IP:32400 - Plex Token - Get from Plex support guide
- TMDb API Key - Get free key at themoviedb.org/settings/api
- Media Root Path - Absolute path to your media library
Example Session
🎬 Plex MCP Server - Interactive Configuration
Ready to start? [Y/n]: y
----------------------------------------------------------------------
1. Plex Server Configuration
----------------------------------------------------------------------
Your Plex server URL (typically http://YOUR_IP:32400)
Plex URL [http://localhost:32400]: http://192.168.1.100:32400
Your Plex authentication token
Plex Token: abc123def456...
🔄 Testing connection to Plex server...
✅ Connected successfully to: My Plex Server
----------------------------------------------------------------------
2. TMDb Configuration
----------------------------------------------------------------------
TMDb API Key: xyz789...
🔄 Testing TMDb API key...
✅ TMDb API working!
[continues...]
✅ Configuration Complete!
Next steps:
1. Test the server: uv run --env-file .env videodrome
2. Restart Claude Desktop to pick up new config
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.
- 4d ago First seen · 150 lines · 0 tokens per session scan A 6754234da7e1
configure is a command published in the GitHub repository nickperrott/videodrome-plugin (1 stars, last pushed 6mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,018 tokens. 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 commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.