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/galbaz1/video-research-mcp/getting-startedgit clone --depth 1 https://github.com/Galbaz1/video-research-mcpWrote 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/galbaz1/video-research-mcp/getting-started)<a href="https://agentmods.dev/commands/galbaz1/video-research-mcp/getting-started"><img src="https://agentmods.dev/badge/commands/galbaz1/video-research-mcp/getting-started.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.1 | $0.00016 | $0.00755 |
| Opus 5 | $0.00008 | $0.00378 |
| Sonnet 5 | $0.00003 | $0.00151 |
| Haiku 4.5 | $0.00002 | $0.00076 |
Grade A, and why
getting-started 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 6d 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 — 73 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Getting Started
Welcome the user to the video-research plugin and walk them through first-time setup.
Step 1: Verify Configuration
Read ~/.config/video-research-mcp/.env and check:
- Is
GEMINI_API_KEYset (uncommented, non-empty)? - If not: tell them to get a free key at https://aistudio.google.com/apikey, paste it in that file, and restart Claude Code. Stop here.
If the key exists, call infra_configure() with no arguments to confirm the server is responding.
- If it responds: report the active model and move to Step 2.
- If it fails: tell them to restart Claude Code and try again.
Step 2: Quick Smoke Test
Run a simple web search to prove everything works:
web_search(query="latest AI research news", num_results=3)
If it succeeds, briefly confirm with: "Your setup is working. Here's what you can do."
If it fails, report the error and suggest /gr:doctor quick for diagnostics.
Step 3: Show What's Available
Present this reference. Use a compact format — no verbose descriptions.
Commands (type these in Claude Code)
Research & Analysis (/gr:)
| Command | What it does |
|---|---|
/gr:research "topic" |
Deep research with evidence tiers |
/gr:research-doc |
Research grounded in your documents (PDFs, URLs) |
/gr:search "query" |
Quick web search via Gemini |
/gr:analyze |
Analyze any content — URL, file, or text |
/gr:video <url> |
Analyze a YouTube video or local file |
/gr:video-chat |
Multi-turn Q&A about a video |
/gr:recall "topic" |
Search past analyses and research |
/gr:ingest |
Add knowledge to the store manually |
/gr:models |
View or change the Gemini model preset |
/gr:doctor quick |
Health check — verify all connections |
Video Explainer (/ve:)
| Command | What it does |
|---|---|
/ve:explainer |
Full explainer video workflow |
/ve:explain-video |
Analyze content, then create explainer |
/ve:explain-status |
Check video project status |
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.
- 6d ago First seen · 73 lines · 16 tokens per session scan A 3f22e39ab30d
getting-started is a command published in the GitHub repository Galbaz1/video-research-mcp (23 stars, last pushed 1mo ago), licensed MIT. It adds 16 tokens to every session and 755 once invoked, about $0.0001 per session on Opus 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-30.
Other commands, from other repositories
setup-video-vision
Interactive setup wizard for claude-video-vision — configure backend, whisper, frames, and verify dependencies.
eg-new-feature
Build a new feature using the elephant/goldfish workflow — design doc, goldfish design check, implement, review, validate.
eg-fix-bug
Fix a bug using the elephant/goldfish workflow — problem doc, goldfish diagnosis check, failing test, fix, review, validate.
dock-chat
Dock the full conversation to Telegram — drive Claude from your phone.
mem-last
Prints latest memory cards for the current project.
mem-prune
Removes old low-importance memories.