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/watchgit 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/watch)<a href="https://agentmods.dev/commands/nickperrott/videodrome-plugin/watch"><img src="https://agentmods.dev/badge/commands/nickperrott/videodrome-plugin/watch.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.00899 |
| Opus 5 | $0.00000 | $0.00449 |
| Sonnet 5 | $0.00000 | $0.00180 |
| Haiku 4.5 | $0.00000 | $0.00090 |
Grade A, and why
watch 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 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.
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 — 141 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/videodrome:watch - Manage File Watcher
Control the background file watcher for automatic ingest processing.
Usage
/videodrome:watch [start|stop|restart|status]
Arguments
start- Start the file watcherstop- Stop the file watcherrestart- Restart the watcher (stop + start)status- Show current watcher status (default)
Examples
/videodrome:watch
/videodrome:watch start
/videodrome:watch stop
/videodrome:watch restart
What it does
Start
- Validates PLEX_INGEST_DIR is configured
- Creates watchdog Observer for configured directory
- Registers event handlers for file creation/modification
- Starts background monitoring thread
- Reports watcher status
Stop
- Stops the watchdog Observer
- Processes any pending queue items
- Gracefully shuts down monitoring thread
- Reports final statistics
Restart
- Executes stop sequence
- Waits for clean shutdown (5s timeout)
- Executes start sequence
- Reports new watcher status
Status (default)
- Watcher running state
- Watched directory path
- Files processed since start
- Current queue size
- Last event timestamp
How Auto-Ingest Works
When a file appears in the ingest directory:
-
Stability Check (60 seconds)
- Monitor file size every 10 seconds
- Proceed only when size is stable (no changes)
- Prevents processing incomplete downloads
-
Identification
- Parse filename with guessit
- Query TMDb for matches
- Calculate confidence score
-
Routing Decision
- If confidence >= threshold AND auto_ingest enabled:
- Automatically process (identify + rename + copy + scan)
- Log to history
- If confidence < threshold OR auto_ingest disabled:
- Add to manual review queue
- Notify user (if notifications configured)
- If confidence >= threshold AND auto_ingest enabled:
-
Cleanup
- Remove from watch queue
- Update statistics
Safety Classification
Write Operation - Requires confirmation when starting.
The watcher itself is read-only, but enabling it allows automatic file ingestion which modifies the filesystem.
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 · 141 lines · 0 tokens per session scan A 9012566523c4
watch 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 899 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.